[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: fetching multiple tags
From: |
Eric Siegerman |
Subject: |
Re: fetching multiple tags |
Date: |
Wed, 5 Feb 2003 12:11:21 -0500 |
User-agent: |
Mutt/1.2.5i |
On Wed, Feb 05, 2003 at 10:14:51AM -0500, CHARLES HART, BLOOMBERG/ 499 PARK
wrote:
> The second checkout replaces any file that has a B tag (and leaves
> behind any file that should be deleted as-of B I think).
No; the second checkout will not leave such files behind; it'll
delete them. It will do its best to leave you with *only* the
files (and the revisions of those files) tagged with B. The only
exceptions I can think of are:
- uncommitted changes; CVS will merge them rather than
clobbering them
- files not in CVS at all ("?" status); those will be left
alone
> A scripted approach, which would be more efficient is to collect the
> list of files and revisions first, and then get only the "good" ones.
I believe that's the only approach that will work.
> Though I
> don't have an example database handy with deleted files, so I can't
> say what to do about discarding them from the list.
Hmmm. In theory, this should probably just work -- deletion is
just another revision, with a commit date. But I bet that in
practice there'll be ugliness involved :-(
But as Larry said to the original poster:
> No. You're expected to tag all the files in a module,
> not just some of them.
Indeed. In CVS, tags are meant to label the state of the module
at a given point in time, not the transitions. For the latter
(and given that you've tagged the states in the first place), use
"cvs diff -rtag1 -rtag2".
--
| | /\
|-_|/ > Eric Siegerman, Toronto, Ont. address@hidden
| | /
A distributed system is one on which I cannot get any work done,
because a machine I have never heard of has crashed.
- Leslie Lamport
- fetching multiple tags, CHARLES HART, BLOOMBERG/ 499 PARK , 2003/02/05
- Re: fetching multiple tags,
Eric Siegerman <=