[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Strange "CVS update -C" behavior
From: |
Matthew Versluys |
Subject: |
Re: Strange "CVS update -C" behavior |
Date: |
Thu, 1 Nov 2001 14:31:57 -0800 |
Still happens in the 1.11.1p1 with the win32 client.
(btw is ftp://ftp.cvshome.org down, had to find a mirror)
cvs --ver
Concurrent Versions System (CVS) 1.11.1p1 (client)
cvs update -C test.txt
(Locally modified test.txt moved to .#test.txt.1.6)
cvs [server aborted]: cannot open test.txt for copying: No such file or
directory
cvs update test.txt
RCS file: /drive1/cvs/Test/test.txt,v
retrieving revision 1.6
retrieving revision 1.7
Merging differences between 1.6 and 1.7 into test.txt
M test.txt
cvs update -C test.txt
(Locally modified test.txt moved to .#test.txt.1.7)
U test.txt
Cheers,
Matt.
----- Original Message -----
From: "Larry Jones" <address@hidden>
To: "Matthew Versluys" <address@hidden>
Cc: <address@hidden>
Sent: Thursday, November 01, 2001 8:28 AM
Subject: Re: Strange "CVS update -C" behavior
> Matthew Versluys writes:
> >
> > 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.
>
> That bug was fixed in CVS 1.11.1.
>
> -Larry Jones
>
> That's the problem with nature. Something's always stinging you
> or oozing mucus on you. -- Calvin
>