Community technical support mailing list was retired 2010 and replaced with a professional technical support team. For assistance please contact: Pre-sales Technical support via email to sales@march-hare.com.
It looks like it works in the local mode but not in the client server mode. Even if updating -rHEAD is redundant it's possible and it sets the sticky tag attribute, I'm not sure if it used to do that, plus now it produced some wierd results when adding file. Example: C:\sb\Simple>cvs ver Client: Concurrent Versions System (CVSNT) 2.5.01 (Travis) Build 1969 (client/server) Server: Concurrent Versions System (CVSNT) 2.5.01 (Travis) Build 1969 (client/server) C:\sb\Simple>cvs up -A cvs server: Updating . C:\sb\Simple>echo test.txt > test.txt C:\sb\Simple>cvs add -r FIX1 test.txt cvs server: scheduling file `test.txt' for addition cvs server: use 'cvs commit' to add this file permanently C:\sb\Simple>cvs commit -m"add to branch" test.txt RCS file: /CVSTestData/Simple/test.txt,v done Checking in test.txt; /CVSTestData/Simple/test.txt,v <-- test.txt initial revision: 1.1 done C:\sb\Simple>cd .. C:\sb>set CVSROOT=:local:c:/cvsrepo C:\sb>cvs co tmp cvs checkout: Updating tmp U tmp/a.b.c.d U tmp/cannonpa1.c C:\sb>cd tmp C:\sb\tmp>ls a.b.c.d cannonpa1.c C:\sb\tmp>cvs up -A cvs update: Updating . C:\sb\tmp>echo test2.txt > test2.txt C:\sb\tmp>cvs add -r test_branch test2.txt cvs add: scheduling file `test2.txt' for addition on branch `test_branch' cvs add: use 'cvs commit' to add this file permanently C:\sb\tmp>cvs ci -m"Add test2.txt to branch" test2.txt RCS file: c:/cvsrepo/tmp/test2.txt,v done Checking in test2.txt; c:/cvsrepo/tmp/test2.txt,v <-- test2.txt new revision: 1.1.2.1; previous revision: 1.1 done C:\sb\tmp>cvs ver Concurrent Versions System (CVSNT) 2.5.01 (Travis) Build 1969 (client/server) "Tony Hoyle" <tmh at nodomain.org> wrote in message news:d6e15e$k6t$1 at paris.nodomain.org... > Matt Schuckmann wrote: > > > I updated the sandbox with the command. > > cvs up -A -r HEAD > > That's redundant.. it'll produce a really odd entries file (which should > normally be coped with but may be server dependent). > > > I executed the add command > > cvs add -rFIX1 e.cpp > > > > I get the following message. > > cvs server: scheduling file `e.cpp' for addition on branch `HEAD' > > cvs server: use 'cvs commit' to add this file permanently > > That's not what happens for me at all... what version are you using? > > D:\t>cvs ver > Concurrent Versions System (CVSNT) 2.5.01 (Travis) Build 1969 > (client/server) > > D:\t>cvs up -A > ... > D:\t>cvs add -r test_branch test.txt > cvs add: scheduling file `test1.txt' for addition on branch `test_branch' > cvs add: use 'cvs commit' to add this file permanently > > D:\t>cvs commit -m "add to branch" test.txt > RCS file: d:\repo/test/test.txt,v > done > Checking in test.txt; > d:\repo/foo/test.txt,v <-- test1.txt > new revision: 1.1.2.1; previous revision: 1.1 > done