Strange "CVS update -C" behavior

[Matthew Versluys]

If I'm working on a file and then realize I want to discard my changes I can
use cvs update -C to get a clean copy.  Using cvs 1.11 win32 command line
client, this command doesn't work if someone else has committed a newer
version of the file in the mean time.

for example;

cvs update -C test.txt
(Locally modified test.txt moved to .#test.txt.1.5)
cvs [server aborted]: cannot open test.txt for copying: No such file or
directory

if I do this though it works fine;

cvs update test.txt
RCS file: /drive1/cvs/Test/test.txt,v
retrieving revision 1.5
retrieving revision 1.6
Merging differences between 1.5 and 1.6 into test.txt
M test.txt

cvs update -C test.txt
(Locally modified test.txt moved to .#test.txt.1.6)
U test.txt


Is there a reason that update -C doesn't just get a clean copy regardless ?

It appears that Noel L Yap submitted a patch for cvs update -C behavior on
Jan 15, 2001 in response to a message from Stephen Rasku on Jan 12, 2001 but
for some reason I can't access the ccvs repository at cvshome.org at the
moment to see what's been going on in src\update.c to see when/if the patch
was applied and if it fixes the problem

Cheers,
Matt.