> OK. Another tack would be to do what you suggest on the main tree, and
> then backpatch using diffs on the entire tree. Then we can release on
> the v6.5.x branch as we would have liked.
Why not just use the current tree. What does backpatching the entire
tree do for us?
>
> I'll be happy to attempt the backpatching, and if I fail then we can
> proceed with a v6.5.2 release based on the main tree. But I'm more
> comfortable knowing that we've inspected every patch, and included
> only those which address something significant.
Oh, yes. I see. Good idea to just review the patches and see what is
involved. It is actually pretty easy to do that in one big patch.
> Does this sound unrealistic? I'm guessing that the backpatching can
> happen fairly easily, but I don't understand why someone just reported
> 3.5MB of diffs. Hmm, how much of those diffs are on the docs tree? I
> did make a bunch of changes to get the man pages going, and they
> aren't relevant for v6.5.2 which could be limited to the src/ tree.
Don't know.
--
Bruce Momjian | http://www.op.net/~candle
maillist@candle.pha.pa.us | (610) 853-3000
+ If your life is a hard drive, | 830 Blythe Avenue
+ Christ can be your backup. | Drexel Hill, Pennsylvania 19026
