Stephen Rasku wrote : || What I don't understand is: If something is bad, why is it allowed. || If using this feature is dangerous, then it should be removed from || CVS. It's not so much "bad" as it is irrelevant to the CVS way of doing things - a distraction retained from historical roots. Until very recently, cvs used the rcs suite of programs for version storage, and rcs, when not wrapped up as a part of cvs, has a significant value for managing version numbers. Removing it (to the extent that parts of cvs would fail to work correctly) would make huge numbers of existing cvs repositories be broken - not a step to be taken lightly unless you want to have people refusing to upgrade for years, rather than take the time to rebuild their repositories (and possibly their build processes). -- Sleep should not be used as a substitute | John Macdonald for high levels of caffeine -- FPhlyer | [EMAIL PROTECTED]
- Re: ".trunk" patch refinement David Thornley
- Re: ".trunk" patch refinement Russ Allbery
- Re: ".trunk" patch refinement John Macdonald
- Re: ".trunk" patch refinement Eivind Eklund
- When is it appropriate to update a major version... Mike Jellison
- Re: When is it appropriate to update a major... Larry Jones
- Re: When is it appropriate to update a major... Laird Nelson
- Re: When is it appropriate to update a m... Greg A. Woods
- RE: ".trunk" patch refinement Cameron, Steve
- RE: ".trunk" patch refinement Stephen Rasku
- RE: ".trunk" patch refinement John Macdonald
- RE: ".trunk" patch refinement Cameron, Steve
- RE: ".trunk" patch refinement Greg A. Woods
- Re: ".trunk" patch refinement John P Cavanaugh
- Re: ".trunk" patch refinement David Thornley
- RE: ".trunk" patch refinement Cameron, Steve
- RE: ".trunk" patch refinement Fabrice Lavier
- RE: ".trunk" patch refinement Cameron, Steve
- RE: ".trunk" patch refinement Stephen Cameron
- Re: ".trunk" patch refinement John P Cavanaugh
- Re: ".trunk" patch refinement Stephen Cameron
