Re: Commit log edits lost when commit fails

[TimC]

On 2006-11-29, Mark D. Baushke (aka Bruce)
  was almost, but not quite, entirely unlike tea:
> TimC <address@hidden> writes:
>
>> I'm using cvs version 1.11.17, and tried to commit a file, when a
>> network error happened:
>> 
>> > cvs commit iter2.p
>> trying GNU_PORT=21816
>> cvs [commit aborted]: end of file from server (consult above messages if any)
>> >
>> 
>> It unlinked the /tmp/cvs* file that was associated with this, despite
>> the other error conditions leaving a file:
>> > cvs commit asd
>> trying GNU_PORT=21816
>> cvs server: Up-to-date check failed for `asd'
>> cvs [server aborted]: correct above errors first!
>> cvs commit: saving log message in /tmp/cvsMKtGP7
>> >
<snip> 
> No version of CVS does anything with a ChangeLog file out-of-the-box.

I mean the commit log.

> I have never seen the 'trying GNU_PORT=21816' message before.

Sorry, when I was snipping, I failed to snip the debug message (to
stderr) from my $EDITOR.

> I suggest you need to chat with your own cvs administrator to see how
> they have setup your local site CVSROOT/{commitinfo,verifymsg,loginfo}
> scripts.

I am my administrator.  They're as default provided by cvs, but I
don't think they're relevant, because they decide whether the server
allows the commit or not, but it was a network failure that forced the
abort.  In other cases of failure, the cvs client will leave the
temporary file lying around, so you can fix the problem, reload the
temporary file, and recommit, but in this case, the temporary file was
deleted despite the failure, so I wasn't able to reload the log when I
fixed the network problem.

-- 
TimC
"Warning: Do not look into laser with remaining eye" -- a physics experiment
"Press emergency laser shutdown button with remaining hand" -- address@hidden