... and the debate continues! All very interesting - that's for certain. For the time (and lack of!) I'm going to just use the structure I devised and manage it that way. Should I become more of a "cvs power-user" in the future (and still lack commit kudos), I may well examine other possibilities. For now, I need to get this done and move on with life (and work!). While what you all propose sounds very doable - if only by me locally (ie - checking the tree into my own CVS and branching that - I have full control over it) I think my knowledge is somewhat lacking to make it efficient.
Thanks though ;-) Daniel Honig wrote: >Well this is exactly the manner that I used PVCS another SCS a commercial >from merant >that I'm sure many listees have encountered. > >Now the needs/challeneges of my teams are probably not as great as >open source development. But I was thinking in concept you should >be able to create a branch for each patch and track the patch >as that branch. > >-Daniel > -- Eddie Bush -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
