> Doing a switch to a different tree than trunk is for me somewhat > easier than applying a patch. (At least sometimes)
But may not be easy for others, and is not making my life any easier. I understand that it will make backporting a lot easier if a feature is committed to the 1.5.x tree as a correct, complete one. But if we can not find an easy way to let more people test the patch before it is applied, can we loosen this a little bit? What I need from you, more experienced lyx developers, is a quick look at the patch, find logic errors (like JMarc did for my auto-cls-layout patch), design flaws (like the bundling of lastfile with lastpos), or better implementations. If the patch *looks* fine, I will submit to the trunk and let others have the chance to use and test it. Does this sound OK to you? I will wait another week, till I force my patches (view-source and auto-cls-layout) into the trunk. Bo
