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.
One of the changes that was made in 57g was to propagate the '-c' commit
flag, which checks to see if the user is a valid editor of the file before
committing it. There are two ways to get around it:
1) Check to see if you have the -c flag set for commit in your .cvsrc, or,
if you are using WinCVS or the like, check to make sure that the "Check for
valid edits" check box is unchecked first.
2) Edit the file using cvs edit prior to committing it.
Boyd
-----Original Message-----
From: cvsnt-admin at cvsnt.org [mailto:cvsnt-admin at cvsnt.org]On Behalf Of
Juanma Barranquero
Sent: Tuesday, September 03, 2002 2:24 AM
To: Tony Hoyle
Cc: cvsnt at cvsnt.org cvsnt downloads at march-hare.com @CVSNT on Twitter CVSNT on Facebook
Subject: Re: [cvsnt] user xxx is not a valid editor of the file yyyyy
On Mon, 02 Sep 2002 10:53:24 GMT, tmh at nothing-on.tv (Tony Hoyle) wrote:
> Presumably somone has done a 'cvs edit' on the file.
No.
I have the CVSNT server running on my machine and I'm the only one to
use it. And the troubling file is only checked out once, in the
directory where I tried the commit.
Moreover, I deinstall 57g/h, reinstall 57f, do commit and it works. If I
switch back to g or h, modify the file and commit, it again fails to
work.
/L/e/k/t/u
_______________________________________________
cvsnt mailing list
cvsnt at cvsnt.org cvsnt downloads at march-hare.com @CVSNT on Twitter CVSNT on Facebook
http://www.cvsnt.org/cgi-bin/mailman/listinfo/cvsnt https://www.march-hare.com/cvspro/en.asp#downcvs