Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
From: "Hannu E K Nevalainen" <garbage_collector AT telia DOT com>
To: <cygwin AT cygwin DOT com>
Subject: RE: CVS + SSH + Binary File = ^M
Date: Mon, 19 Apr 2004 22:37:57 +0200
Message-ID: <NGBBLLIAMFLGJEOAJCCEGEDNDKAA.garbage_collector@telia.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
In-reply-to: <NUTMEGmiPiqRn60xPns000004f7@NUTMEG.CAM.ARTIMI.COM>

> From: Dave Korn
> Sent: Monday, April 19, 2004 5:29 PM

Commenting a message from kgrizzle
> > Sent: 19 April 2004 16:15

> Basically I think it's a bad idea to mount your filesystems in textmode
> and then complain "But it keeps adding \r to my line endings".
> Accessing a binary file through a textmode mountpoint is a dubious
> thing to expect to work.  I personally think the most reliable strategy
> is to accept that we're working with a POSIX system, standardize on
> Unix EOLs throughout your files, mount your filesystems in binary mode,
> and only ever have Unix<=>DOS EOL conversions by deliberately invoking
> d2u/u2d manually.

I can only agree with the above; I've been using this strategy for a couple
of decades - yet to be bitten hard.

My situation for a long time:
 AmigaOS (LF line endings)
   <= versus =>
 MS DOS and whatever came after it (The well known CRLF line endings)


/Hannu E K Nevalainen, B.Sc. EE - 59+16.37'N, 17+12.60'E

** on a mailing list; please keep replies on that particular list **

-- printf("LocalTime: UTC+%02d\n",(DST)? 2:1); --
--END OF MESSAGE--


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/