Date: Thu, 14 Dec 2000 13:21:34 -0500
Message-Id: <200012141821.NAA24932@envy.delorie.com>
X-Authentication-Warning: envy.delorie.com: dj set sender to dj AT envy DOT delorie DOT com using -f
From: DJ Delorie <dj AT delorie DOT com>
To: djgpp-workers AT delorie DOT com
In-reply-to: <Pine.SUN.3.91.1001214115151.25353P-100000@is> (message from Eli
	Zaretskii on Thu, 14 Dec 2000 11:52:36 +0200 (IST))
Subject: Re: MS-DOS path support in CVS
References:  <Pine DOT SUN DOT 3 DOT 91 DOT 1001214115151 DOT 25353P-100000 AT is>
Reply-To: djgpp-workers AT delorie DOT com
Errors-To: nobody AT delorie DOT com
X-Mailing-List: djgpp-workers AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk


> I think CVS should use binary I/O by default and have an optional
> switch to use text-mode I/O.  This will DTRT in most of the cases:

CVS files have a flag within them that says if the file should be
binary or text.  If the flag says binary, the files must be checked in
and out in binary.

If the file is supposed to be text, I propose this:

* When checking out, write the file in binary mode so that line
  endings are unix-compatible.

* When checking in, read the file in text mode in case the user used a
  DOS editor on it.

Note that I prefer that this mode be enabled with, say, an entry in
.cvsrc ($HOME/cvs.ini?) rather than be the default.  I'd prefer the
default to check out text files with CRLF so that the user can use
their favorite DOS editor, whether it supports unix text format or
not.

A "cvs diff" needs to deal with CRLF/NL conversions automatically for
text files.