[cvsnt] command cvs -n update

Devin dlandespub at gmail.com
Tue Oct 3 23:18:20 BST 2006

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.

Tony Hoyle <tony.hoyle at march-hare.com> wrote in
news:dqr0qk$q33$1 at paris.nodomain.org: 

> Alain Gauthier wrote:
>> Dear all
>> I work with CVSNT as client on Windows XP and a CVS server on Linux.
>> On the client side, I type the command 'cvs -n update foo' on the DOS
>> command line interface :
>> In case of conflict or a need to merge with 'foo' I get not only the
>> update command output but  also 'foo' is modfied
>> as if I performed the command without option '-n'.
>> So foo is modified indicating the conflict blocks and the .#foo is
>> created. 
> -n is only supported for 'co -n' on an empty directory (as used to 
> simulate ls on servers that don't support it and by things like
> eclipse) - the latest documentation has been updated to reflect this.
> Supporting it for all commands is just too complex - it never really 
> worked... even on the old cvs it sometimes modified the sandbox, and
> its implementation is just a mess (lots of conditions littered all
> over the code).  There are plenty of other ways to find out
> information about the repository that are nondestructive.
> Tony

You should disable -n by default. CVSNT should die if -n is used in a 
place where it doesn't work. A flag/registry setting/environment 
variable would exist to make it silently ignore -n as it does now.

I got burned by this thing. Please fix :)

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