[Top][All Lists]

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

Re: CVS tag problem, please help

From: Eric Siegerman
Subject: Re: CVS tag problem, please help
Date: Tue, 24 Jul 2001 21:13:08 -0400
User-agent: Mutt/1.2.5i

On Tue, Jul 24, 2001 at 02:41:31PM -0700, Teala Spitzbarth wrote:
> > [restarting an aborted "cvs tag"]
> You if your working copy is OK with what you want to tag
> you should be able to restart the tag process after you clear
> up the lock files....  

Yes.  Just rerun the "cvs tag mytag" command.  The individual
files fall into three cases:
 1. Files that haven't been tagged yet:
        They'll get the tag applied to them, and a "T file" line
        will be printed.  Just like usual.

 2. Files that were tagged by the aborted command (and you're
    trying to retag the same revision):
        CVS will silently ignore these; it won't even print a
        "T file" line for them.

 3. Files that were tagged by the aborted command (but you're now
    trying to apply "mytag" to a DIFFERENT revision):
        CVS will consider this an error.  I can't remember whether
        it aborts the whole operation, or just prints a message
        and goes on tagging other files, but in any case, it will
        NOT change the tag on these file.

If you restart the tag in the same sandbox, and you haven't done
any updates or commits in that sandbox since the abort tagging
operation, you shouldn't have to deal with any case-3 files.  I
just mentioned that case for completeness, and to reassure you
that restarting the tag command won't do anything dangerous.

Note for future reference that if you *want* CVS to change the
tag on case-3 files, instead of reporting an error, you can use
the "cvs tag -F" option.  But that's not the situation for you
right now, so please don't use "-F" this time.

If you want to convince yourself that all the files got tagged,
you can do any combination of these:
  - Do the tagging in two steps:
        cvs tag -d mytag
        cvs tag mytag
    The first command will remove all the tags put in by the
    aborted run.  That'll put all the files into case 1, so the
    second command will print "T file" lines for them all.  But
    it'll take longer.

  - Run "cvs status -v" afterwards, and inspect the output

  - Check out a new sandbox using "-r mytag" afterwards, and
    compare it to the sandbox you issued the tag command from


|  | /\
|-_|/  >   Eric Siegerman, Toronto, Ont.        address@hidden
|  |  /
With sufficient thrust, pigs fly just fine. However, this is not
necessarily a good idea.
        - RFC 1925 (quoting an unnamed source)

reply via email to

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