Date: Fri, 15 Dec 2000 12:43:17 +0200 From: "Eli Zaretskii" Sender: halo1 AT zahav DOT net DOT il To: dj AT delorie DOT com Message-Id: <5567-Fri15Dec2000124317+0200-eliz@is.elta.co.il> X-Mailer: Emacs 20.6 (via feedmail 8.3.emacs20_6 I) and Blat ver 1.8.6 CC: djgpp-workers AT delorie DOT com In-reply-to: <200012142236.RAA26863@envy.delorie.com> (message from DJ Delorie on Thu, 14 Dec 2000 17:36:58 -0500) Subject: Re: MS-DOS path support in CVS References: <200012141821 DOT NAA24932 AT envy DOT delorie DOT com> <200012142234 DOT RAA24937 AT indy DOT delorie DOT com> <200012142236 DOT RAA26863 AT envy DOT delorie DOT com> 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 > Date: Thu, 14 Dec 2000 17:36:58 -0500 > From: DJ Delorie > > > This doesn't work with DOS batch files. If you read it in text mode, > > the CRs get stripped away. After that, checking it out will write it > > in binary mode, with Unix-style LFs, and you get an unusable batch > > file, because COMMAND.COM won't run it. > > I suspect that, in this case, the user should tag that file as binary > so that the CRs are always preserved, no matter what. This is a solution, but I don't like it. Tagging a file as binary means you lose diffs and per-line annotations, which IMHO is quite a loss. (This is not a theoretical problem: many GNU packages nowadays include batch files used to configure them for DJGPP. I hit this problem each time I need to check in or check out those batch files from the repective CVS repositories.)