From: Guy Gascoigne - Piggford <ggp@informix.com>
To: "Jeffrey C. Fried" <Jeff@Fried.net>,
Richard Thomas <richard@smartmedia.co.uk>,
gnu-win32@cygnus.com
Subject: RE: Why text=binary mounts
Date: Mon, 19 Jan 1998 10:32:00 -0000 [thread overview]
Message-ID: <3.0.3.32.19980119100732.01c36e98@pop.pdx.informix.com> (raw)
In-Reply-To: <3.0.5.32.19980115235518.03bc0e40@popd.ix.netcom.com>
At 11:55 PM 1/15/98 -0700, Jeffrey C. Fried wrote:
>That is, if we can agree that certain tools are always applied solely to
>text, then automatic conversion of the native EOL to the single '\n'
>character is the solution which will make these tools work in any
>environment. If we don't agree, then we must always construct 'text' files
>according to the UNIX description of a text file when using the gnuwin32
>tools and so it is not easy to use tools of mixed origin on a non-UNIX
>system (for example emacs under NT will rewrite files with CRLF while bash
>will need these files in LF format). I prefer to use the native format so
>that i don't have to remember which tools produce which results and when i
>have to convert between the two formats.
Good points, I agree with them completely.
Guy
--
Guy Gascoigne - Piggford (ggp@informix.com)
Software Engineer, Informix Software, Inc. (Portland, Oregon)
-
For help on using this list (especially unsubscribing), send a message to
"gnu-win32-request@cygnus.com" with one line of text: "help".
next prev parent reply other threads:[~1998-01-19 10:32 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-01-12 14:09 Gary R. Van Sickle
1998-01-14 3:39 ` Richard Thomas
1998-01-16 2:56 ` Jeffrey C. Fried
1998-01-19 10:32 ` Guy Gascoigne - Piggford [this message]
1998-01-16 2:56 ` Benjamin Riefenstahl
-- strict thread matches above, loose matches on Subject: below --
1998-01-15 15:16 Richard Thomas
1998-01-18 16:07 ` Steven R. Newcomb
1998-01-15 15:16 Gary R. Van Sickle
1998-01-17 23:47 ` Fergus Henderson
1998-01-15 7:26 Immanuel Litzroth
1998-01-13 10:42 Gary R. Van Sickle
1998-01-15 7:26 ` Peter Dalgaard BSA
1998-01-17 11:00 ` John A. Turner
1998-01-12 10:42 marcus
1998-01-13 10:53 ` Benjamin Riefenstahl
1998-01-12 9:17 marcus
1998-01-10 6:19 Tony Pires
1998-01-10 13:49 ` Christopher Faylor
1998-01-09 18:22 Gary R. Van Sickle
1998-01-12 2:57 ` Benjamin Riefenstahl
1998-01-09 18:22 Gary R. Van Sickle
1998-01-12 20:11 ` Guy Gascoigne - Piggford
1998-01-09 18:22 Gary R. Van Sickle
1998-01-11 10:01 ` Tomas Fasth
1998-01-08 17:20 Gary R. Van Sickle
1998-01-09 13:40 ` Larry Hall (RFK Partners Inc)
1998-01-09 13:40 ` Tomas Fasth
1998-01-11 23:40 ` Fergus Henderson
1998-01-12 5:03 ` Tomas Fasth
1998-01-12 4:45 ` Fergus Henderson
1998-01-12 17:26 ` Guy Gascoigne - Piggford
1998-01-08 8:31 marcus
1998-01-09 5:51 ` Benjamin Riefenstahl
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3.0.3.32.19980119100732.01c36e98@pop.pdx.informix.com \
--to=ggp@informix.com \
--cc=Jeff@Fried.net \
--cc=gnu-win32@cygnus.com \
--cc=richard@smartmedia.co.uk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).