Here is how Mark and I have agreed on those sort of things. If such a patch is accepted in 3.4.x but not in 4.0.x, then we've introduced aregression in 4.0.x. So, the way we deal with it is that, the patch is first applied to4.0.x, then to 3.4.x retrospectively. Is that workable for you?
Absolutely. I actually did all the workin in a 4.0.2 cvs tree, and Im backporting it to my 3.4.5 tree.
Kean
