Larry Jones wrote: > > Todd Denniston writes: > > > > Assuming the "-t" was really "-r", this is the expected behavior... > > No, it is not. Expected behavior is for CVS to remove files that are > under its control that do not contain the specified tag, but the > original message said that it removed "things not yet in cvs", which it > should never do. And I'm reasonably certain that it doesn't, so the > original poster must be mistaken or described it incorrectly. > > -Larry Jones You are of course, correct. I missed the "things not yet in cvs" part.
For penitence I submit the following script for use in verification on the troubled user's system. I executed with with Concurrent Versions System (CVS) 1.11.16 (client/server) and got the following results. It does as Larry indicates, b.txt still exists at the end, and it also does what I thought I was indicating (cvs controlled files that are not tagged are removed from the sandbox), i.e., the testdir/CVSROOT/ dir and files are not in the sandbox at the end. cd /tmp/ mkdir junktest cd junktest/ export CVSROOT=/tmp/junktest/Repo mkdir Repo cvs init cvs checkout -d testdir . cd testdir/ ls -l > a.txt cvs add a.txt cvs commit -m commitmsg ls -ltrh >> a.txt cvs commit -m commitmsg ls -ltrh >> b.txt cvs tag PROD a.txt cvs update -r PROD ls -ltrh cvs update -r PROD -P -d ls -ltrh -- 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
