Re: ChangeLog edits lost when commit fails

[Mark D. Baushke]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

No version of CVS does anything with a ChangeLog file out-of-the-box.

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

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.

        Good luck,
        -- Mark

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
> >
> 
> Is this bug still present in uptodate cvsen?
> 
> It's hard to reproduce any old network error on demand, so I can't
> check without looking at the source.
> 
> -- 
> TimC
> "How should I know if it works?  That's what beta testers are for.  I only
> coded it."        (Attributed to Linus Torvalds, somewhere in a posting)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.4 (FreeBSD)

iD8DBQFFbO1BCg7APGsDnFERAu7JAJ9Y0kGP1OEApvDoCJkuCLldL2fkWACg32lT
f0hlo1bk+ruqD/yz5e+RFdQ=
=OYEh
-----END PGP SIGNATURE-----