I use rtag command on a nightly basis to tag the top of our tree, and then pull from that tag to do our nightly builds.
I've never seen any instance where all files in the module were not tagged (i.e. this would result in a build failure for us if it did...), and the rtag command used in this way does select the most recent revision on the trunk. Cheers, Teala -----Original Message----- From: Larry Jones [mailto:[EMAIL PROTECTED]] Sent: Monday, May 13, 2002 8:18 AM To: Jay Glanville Cc: [EMAIL PROTECTED] Subject: Re: rtag not tagging everything? Jay Glanville writes: > > I just rtaged a module using the command: > cvs rtag TPM_01_02_00_01 source That is a dangerous (some might even say meaningless) command -- exactly what revision of each file did you intend to tag? You didn't say, so you don't really know what you tagged. > However, when I perform a > cvs log [filename] > on some files in the source module, I don't see the tag I stated. And it's > inconsistant. I can see it on some files, but not on others. Since you didn't tell CVS exactly what to tag, you shouldn't be surprised that you didn't get what you want. To be honest, I'm not entirely sure what happens when you use rtag without specifying a particular revision. My guess is that it tags the most recent revision on the trunk, so any files that don't exist on the trunk (either they only exist on a branch or they've been deleted and don't exist anywhere) won't be tagged. -Larry Jones Archaeologists have the most mind-numbing job on the planet. -- Calvin _______________________________________________ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs _______________________________________________ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
