RE: rtag -r <tag> not tagging files in Attic???

[Teala Spitzbarth]

No.... if you have new files added to a branch - they 
are in the attic - not all files in the attic are "dead".
I don't know if Steve's issues were with new branch 
files in the Attic. But even if not... I would expect
that if the <existing tag> is present on a removed file
in the attic - it should get the re-tag.  The reason removed 
files exist in the attic is to provide operations on old tags.

Cheers,
Teala



-----Original Message-----
From: Alexander Kamilewicz [mailto:address@hidden
Sent: Monday, August 13, 2001 1:39 PM
To: 'address@hidden'
Subject: Re: rtag -r <tag> not tagging files in Attic???


That seems like correct behaviour to me.  Files in the Attic are
considered "dead", so they shouldn't be a part of any "release".

> "Nesbitt, Steve" wrote:
> 
> All:
> 
> I expected that rtag -r <existing tag> <newtag> module would apply
> <newtag> to *all* files in <module> on which the <existing tag> was
> placed.
> 
> What I'm finding is that if a file that has <existing tag> has been
> placed in the attic, then the <newtag> is not applied to these files.
> 
> Is this the correct behavior? A known bug? Is there a work around?
> (CVS server is running version 1.10.2)
> 
> To provide some context, what I'm trying to do is pautomate placement
> of a label based on the results of a build. Here's the algorithm:
> 
> 1) CVS rtag <build identifier> <sources>
> 2) cvs co -r <build identifier> <sources>
> 3) perform build
> 4) if build was successful move LATESTGOOD tag to sources which are
> also tagged with <build identifier>
> 
> Thanks!
> 
> -steve
> 
> Steve Nesbitt
> Configuration Manager
> The Cobalt Group, Inc.
> 2200 First Avenue South
> Seattle, WA 98134
> address@hidden
> www.cobaltgroup.com
> If it's automotive and it's Internet, it's Cobalt.

_______________________________________________
Info-cvs mailing list
address@hidden
http://mail.gnu.org/mailman/listinfo/info-cvs