Configuration: CVS 1.10.8 Solaris server; CVS 1.10.8 NT client from
WinCVS 1.1b11; using pserver protocol.
I'm having problems using "BASE" as a revision argument as represented
in the following test case:
> cvs update -A testfile.txt
> cvs status -v testfile.txt
File: testfile.txt Status: Up-to-date
Working revision: 1.2
Repository revision: 1.2 /project/cvs_repository/testfile.txt,v
Sticky Tag: (none)
Sticky Date: (none)
Sticky Options: (none)
Existing Tags:
label1 (revision: 1.1)
label2 (revision: 1.2)
> cvs update -j BASE -j label1 testfile.txt
cvs server: file testfile.txt exists, but has been added in revision
label1
why? (and what does that error message mean?). If I specify a specific
tag or revision number instead of "BASE", the update command works fine:
> cvs update -j label2 -j label1 testfile.txt
RCS file:
/export/home/project/repository/cvs_repository/CM_Tools/xfer/testfile.txt,v
retrieving revision 1.2
retrieving revision 1.1
Merging differences between 1.2 and 1.1 into testfile.txt
I wouldn't consider this a "critical" bug, if it is indeed a bug, but
the behavior is a bit puzzling.
Any insight would be appreciated,
David
