[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Tags and uncommited resources...

From: Denniston, Todd A CIV NAVSURFWARCENDIV Crane, Code 6067
Subject: Re: Tags and uncommited resources...
Date: Mon, 30 Jul 2007 09:23:38 -0500
User-agent: Thunderbird (X11/20070716)

Peter Connolly wrote, On 07/28/2007 12:26 PM:
 1) We have three separate projects that together make up the deployment
assets: Commons, Web, and Testing. First question is: can I TAG all three of
the projects with the same TAG to mark the same mile-stone in all three of
them?! Guessing that it's not a problem but wanted to confirm.

See 2nd answer...

And I _think_ you could even tag all of them with one command:
cvs tag mytag sandbox1 sandbox2 sandbox3

 2) Need to TAG the projects while having some uncommited resources locally
- is this a problem? I seem to recall from the docs that the TAG command
only affects the repository, so any uncommited changes locally should not be
included. Not sure if cvs will insist that they be checked in first?!
Ideally, whatever is in repository at the time the TAG command is issued for
each project should be tagged, and all local changes should be
excluded/ignored. Here is the command I plan on using (after navigating to
each project dir):

The 'cvs tag' command operates on your local sandbox.  If the files
that you want tagged are already in the repository, then you want to
use the 'cvs rtag' command which operates directly on the repository.
See the manual for more details.

Lets be clear here,
although 'cvs tag' works on the revisions checked out into your local sandbox,
 a) it only works on files  that are under CVS control (added and committed),
b) it tags the revision that is checked out, not the physical copy that is in your sandbox, so you need to commit any thing that you have added|removed|modified before applying the tag, if you want what is IN your sandbox to be tagged.

There is nothing preventing you from 'cvs rtag'ing three or more
directories in the same command.  That would be the best way to answer
#1 above, although there's nothing stopping you from rtag'ing each
directory separately (except the increased possibility that someone
will commit files in one directory while you're tagging another).

Use of a date specification can reduce that possibility, and using normal 'cvs tag' you can even contrive the set of files/revisions and then apply a tag against that.
cvs checkout project
cvs update -r1.2 project/FileThatIsAtR1.5.txt
cvs tag mytag project/

Todd Denniston
Crane Division, Naval Surface Warfare Center (NSWC Crane)
Harnessing the Power of Technology for the Warfighter

reply via email to

[Prev in Thread] Current Thread [Next in Thread]