info-cvs
[Top][All Lists]
Advanced

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

Re: TAG and file removing


From: Larry Jones
Subject: Re: TAG and file removing
Date: Wed, 29 Jan 2003 17:15:03 -0500 (EST)

Jean-Baptiste BRIAUD writes:
> 
> A developper had removed a file in a tagged module.
> How is it possible ?

CVS has traditionally treated a request to remove a file with a sticky
tag as a request to remove the tag from the file.  There was some
discussion not too long ago about that and, although there wasn't a lot
of participation, those who did participate seemed to agree that that is
a misfeature and should be removed.  As far as I know, that hasn't
actually happened yet, though.

> I thought a tag in a module was like a "picture" of all files
> revision number of the module, so you can later checkout the module with
> the tag name.
> But if it's possible to remove file
> (remove and commit !!! It's really in the Attic folder on server side) 
> Then, how will I be able to checkout module with tag name ?
> The resulting checkedout module will not reflect the one I had when I
> tagged it !

Now I'm confused.  If the user had checked out a specific tagged
revision (e.g., "cvs co -rcvs1.11.2") and then removed and committed a
file, CVS would simply remove the tag from the file, it would not delete
the file.  If the user did not have a specific tagged revision checked
out, then removing and committing the file would remove the file (from
whatever branch is checked out) but would not remove the tag from the
file.  When a file is removed from the trunk, it is placed in the Attic,
but that doesn't affect your ability to see revisions prior to its
removal; when you ask for a specific revision, CVS also looks for files
in the Attic in addition to files in the normal directory.

Note that it's always possible to remove a tag or to move it to a
different revision; tagging a file does not "lock" it in any way.

-Larry Jones

Another casualty of applied metaphysics. -- Hobbes




reply via email to

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