Matthew Herrmann writes:
>
> 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.
Not forced -- you *can* specify a directory within a module:
cvs rtag bogus module/dir
> 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.
But unless you're the only developer or you have a very tightly
controlled development environment, you have no idea what the latest
revision of the file on the default branch (which may be the vendor
branch rather than the trunk) *is*.
-Larry Jones
Please tell me I'm adopted. -- Calvin
_______________________________________________
Info-cvs mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/info-cvs
