"Jim.Hyslop" wrote: > > Mike wrote: <SNIP> > > When I tried a 'cvs update -t PROD' in one of the directories > > it removed those things not yet in cvs from the directory, > > leaving the one file that had a PROD tag, but also set a > > stick tag to PROD so that I couldn't checkout new updates. > Hmmm... CVS never deletes files it does not know about (except when you use > the 'cvs release -d' command). I've never seen it do that on an update. > > Can you reproduce that behaviour consistently? If so, please post the exact > sequence of commands you used, along with the versions of your CVS client > and server software (cvs --version) <SNIP> Assuming the "-t" was really "-r", this is the expected behavior... at least it is what I expect for checkout, I have USED that behavior with update. there is only one file that meets his selection of the baseline & the tag named PROD, so that is all CVS gives him, because he only tagged one file with PROD.
As I explained in: http://lists.gnu.org/archive/html/info-cvs/2004-12/msg00209.html the following indicate it is a desired behavior. http://lists.gnu.org/archive/html/info-cvs/2004-03/msg00394.html http://lists.gnu.org/archive/html/info-cvs/2003-03/msg00250.html -- Todd Denniston Crane Division, Naval Surface Warfare Center (NSWC Crane) Harnessing the Power of Technology for the Warfighter _______________________________________________ Info-cvs mailing list Info-cvs@gnu.org http://lists.gnu.org/mailman/listinfo/info-cvs
