[cvsnt] how commit -r work?
elim.qiu at gmail.com
Fri Mar 9 18:10:17 GMT 2007
Hi Luigi, Bo and Tim,
Thanks a lot. Yes I should use tag instead of manually assigning rev #.
Actually, with cvsnt, help text by
cvs -H commit
shows nothing about -r option.
It's fine with me not assigning the revision #, Just wondering: all
the files managed by cvsnt will always have revision number of the
form 1.* (i.e. the leading '1' will never be changed) ?
On 3/9/07, Bo Berglund <bo.berglund at telia.com> wrote:
> On Fri, 09 Mar 2007 16:14:34 +0000, Tim Chippington Derrick
> <tim at chippingtonderrick.co.uk> wrote:
> >Don't *ever* try to force the revision numbers - it won't work any
> >more and is associated with a broken way of thinking. This is a
> >*very* common mistake that many people make when they don't
> >understand what is going on. Instead just tag all the files with some
> >meaningful name like "V2.0" and then you can always retrieve that set
> Except periods are not allowed in tags...
> You need tag 'Ver2-0' or something like that.
> >of files with the correct versions by specifying the correct tag on
> >checkout. Trust us on this - you can almost totally ignore the
> >individual version numbers as they don't really help you that much.
> There are no individual *version* numbers, but there are *revision*
> numbers and those are maintained by CVS on a file-by-file basis.
> Nitpicking, I know, but I think that here is a need for correct
> Your message contents is all right! :-)
> (Bo Berglund, developer in Sweden)
> cvsnt mailing list
> cvsnt at cvsnt.org
More information about the cvsnt