[This might answer some of the questions in the comments about "why
binary mode?" :-)

I've also seen this reported on VMS.

I'd have to do some more digging to figure out exactly what is going
on here (maybe it is buggy for non-client/server only, and works for
the client?).

-kingdon]

Date: Wed, 3 Dec 97 18:53:22 PST
To: bug-cvs@prep.ai.mit.edu
From: rayer@ia-us.com

>Submitter-Id:   net
>Originator: 	 rayer@ia-us.com
>Organization:
IA Corp. I, Emeryville, CA.
>Confidential:  no
>Synopsis:	"cvs ci -F" adds carriage returns to committed file
>Severity:	non-critical
>Priority:	medium
>Category: 	cvs
>Class:		sw-bug
>Release:	cvs-1.9.14 and cvs-1.9.20, at least
>Environment:
    	OS2 warp 3.0 (with your precompiled emx.dll and cvs.exe)
System: OS/2 bosrec13 2 2.30 i386
Architecture: i386

>Description:
	Using the -F method of inputting the commitlog reason causes
	cvs to store the carriage returns from the message file, in error.
	For some reason, the vi I'm causes cvs to hang up.
>How-To-Repeat:
	Try it.
>Fix:
	The workarounds:
	1. use "cvs ci -m" (this limits the commitlog entry to one line)
	2. set cvseditor=emacs and use emacs to input the commitlog entry.
	3. strip out the carriage returns from the message file before
	   doing the commit, e.g., ftp the message file to unix in ascii mode,
	   then ftp it back to os2 in binary mode, or other such method.