[cvsnt] Fwd: Re: Bug on "cvs unedit" after a modification followed by a "cvs edit"

capaverde at 3ia.com.br capaverde at 3ia.com.br
Tue Dec 20 11:01:17 GMT 2005

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.

> Frederic Gilles wrote:
>> Hello all,
>> I think I have found a bug on CVSNT.
>> Here is what I do :
>> - I set the read/write status of a file to "writable"
>> - I modify and save the file
>> - I do a "cvs edit" on this file
>> - And when I do a "cvs unedit", it doesn't ask me if I want to revert my
>> changes. But the read/write status changes to "read-only" and the file
>> becomes unedited.
> That's because you have not made any changes since the edit.  It's doing
> the right thing - reverting to the state before the edit as you asked it to.
> You can do unedit -w to leave the file read/write.. historically unedit
> always sets the file read only no matter what its state before.. it's
> debatable whether it should always do this, but as it stands that's the
> way it works.
> Tony


The problem is that after unedit, CVSNT updates the file modification date. If
you do a CVS STATUS, cvs correctly reports it as modified, but WINCVS
don't. It
shows the file as unchanged! I think it's the bug.


More information about the cvsnt mailing list
Download the latest CVSNT, TortosieCVS, WinCVS etc. for Windows 8 etc.
@CVSNT on Twitter   CVSNT on Facebook