RE: Info-cvs Digest, Vol 8, Issue 6

[Matthew Herrmann]

If 'cvs tag' is run from a subdirectory of within a large directory
structure, only files within that section will be given the tag -- that
subdirectory is treated like a module. No error appears because this
operation is valid. Later, when trying to diff between versions of the
software, lots of spurious changes will come up due to the incorrect
tagging. With "cvs rtag", the user is forced to tag every file in the entire
repository.

I always understood that "cvs rtag" without a "-r" would tag the latest
version of all files on the trunk, synonymous with "cvs rtag -rHEAD tagname
module" (?) I had been using it in this manner for some time and not
experienced behaviour to contradict this.

Matthew Herrmann
--------------------------------------
VB6/SQL/Java/CVS Consultancy
Far Edge Technology
http://www.faredge.com.au/

-----Original Message-----
From: Larry Jones [mailto:address@hidden
Sent: Sunday, 6 July 2003 09:43
To: Matthew Herrmann
Cc: address@hidden; address@hidden
Subject: Re: Info-cvs Digest, Vol 8, Issue 6


Matthew Herrmann writes:
>
> The only caveat to this approach is that "cvs tag" should not be used,
only
> "cvs rtag" since you risk polluting your utils project with TAGS from
> multiple projects otherwise. This caveat is not a drawback for me since I
> consider "cvs tag" a dangerous option.

Why?  It's "cvs rtag" when used without the -r option that's truely
dangerous, since you have no way of knowing what revisions you're
tagging.

-Larry Jones

Even if lives DID hang in the balance, it would depend on whose they were.
-- Calvin