I had thought about that. I don't like the idea of having to maintain
that though - it's much more straight-forward (to me) to maintain
seperate trees (as gruesome as it may seem). I need to learn CVS better :-/
My current strategy is looking like:
.../struts/bugs/
jakarta-struts/ ("virgin" code)
by-bugid/
12702/
jakarta-struts/ (includes changes for bugid 12702)
10348/
jakarta-struts/ (includes changes for bugid 12348)
etc ... Nasty as it appears, I think it's probably the "fastest/easiest"
solution.
I'll dig into the cvs texinfo docs and see if I can familiarize myself
enough with branching to use that alternative. I would want my diffs
built with regard to the jakarta cvs tree though - not mine.
Thanks!
Daniel Honig wrote:
>Just for my own curiosity is it possible to solve
>this problem by branching the module that contains the patch?
>
>You would have a nasty time merging it back togehter, but
>this is better than having a copy of the entire tree locally
>for each patch?
>
>Isn't this what branching is for? Am I missing something?
>
>-Daniel
>
--
Eddie Bush
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
