[cvsnt] Re: Increasing release with "commit -r" fails

[Oliver Giesen]

Chuck Kirschman wrote:

> Changing revision numbers is convenient when you make a major change in
> product.  Imagine that between V9 and V10 you rearchitected a large
> chunk of your product and change your file format.  So just prior to V10
> development (V9 branch created) you revision everything up to 10.0.  Now
> when you are reading the log you can easily tell where the product break
> occurred just by the revision number.

This whole idea goes down the drain once you start adding new folders. 
Files committed within those will automatically start at 1.1 again...
(unless you remember to *always* use the -r option for the initial 
commit of course but is that really worth the hassle?).

Cheers,

-- 
Oliver
----	------------------
JID:	ogiesen at jabber.org
ICQ:	18777742	(http://wwp.icq.com/18777742)