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.
Serge, > So please accept the following "unofficial" bug report: > The problem is that after update/merge of conflicting file, > the file was left with RO attribute and conflict editor could > not handle this. Previous version opened conflicting files for > writing. Submitting this report twice does not make it any more legible. Submitting it under the subject "Re: [cvsnt] Re: CVSNT does not support *large* binary files(crashesonthem)" also doesn't make it any more legible. I (any I suspect everyone else on the list) updates/merges quite often and I certainly don't see files becoming read-only after a merge. You'll need to list the actual commands, actual client and server versions, CVSROOT, trace of the "cvs update" (ie: "cvs -ttt update" with server side tracing enabled) and also list the "cvs status" of the file before and after the trace. And choose a relavent subject line. Regards, Arthur Barrett