Mike Jellison writes: > > It seems you saying never update your project to a new major version number, > you should used tags to reflect releases. Correct. > I don't understand why updating a major version number is a bad thing. Because it encourages you to actually pay attention to the version numbers, which you shouldn't do when using CVS. Once you start branching, you get all kinds of weird version numbers -- it's best to learn that they're really just for CVS and people should completely ignore them. People should pay attention to tags instead. > When would it be appropriate to update a major version? > > When would it be appropriate to update an individual file to a new major > version? Never. -Larry Jones The hardest part for us avant-garde post-modern artists is deciding whether or not to embrace commercialism. -- Calvin
- RE: ".trunk" patch refinement Greg A. Woods
- Anybody converted VSS history to CVS? Laine Stump
- RE: ".trunk" patch refinement Rex_Jolliff
- Re: ".trunk" patch refinement David Thornley
- Re: ".trunk" patch refinement Greg A. Woods
- 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
