From: Richard Bland <r.bland@espo.org>
To: cygwin@cygwin.com
Subject: RE: CRLF to LF Issue
Date: Mon, 30 Jun 2003 16:05:00 -0000 [thread overview]
Message-ID: <F668F8488B0EA74D89C887A74FB4116F2BA730@Endor> (raw)
OK, thanks for the hint. I've hacked out reference to O_BINARY in the
function 'create_output_file', and that, amongst other hacks, seems to have
done the trick.
Ta!
Rich
-----Original Message-----
From: Corinna Vinschen [mailto:corinna-cygwin@cygwin.com]
Sent: 30 June 2003 13:50
To: cygwin@cygwin.com
Subject: Re: CRLF to LF Issue
On Thu, Jun 26, 2003 at 11:54:30AM +0100, Richard Bland wrote:
> fashion. If I use 'patch' to apply a patch file to this source code,
> the CRLF pair become a single LF for every line in the file.
Cygwin patch always creates output files in binary (LF EOL). This solves
more problems (discussed earlier in this list and elsewhere) than it
produces so I'm not inclined to revert that change. If you don't like it,
use a Windows native patch or unix2dos.
Corinna
--
Corinna Vinschen Please, send mails regarding Cygwin to
Cygwin Developer mailto:cygwin@cygwin.com
Red Hat, Inc.
--
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/
Note: ESPO currently uses Microsoft Office 2000/XP.
Please make sure that files you send can be read in this format. This
message is intended only for the named addressee(s) and may contain
confidential and/or privileged information. If you are not the named
addressee you should not disseminate, copy, disclose, modify or distribute
this e-mail unless authorised to do so by the sender. If you have received
this message in error then please notify m.geary@espo.org and delete the
message and any attachments accompanying it immediately.
You are also advised that the views and opinions expressed in this e-mail
message and any attachments are the author's own, and may not reflect the
views and opinions of ESPO.
--
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/
next reply other threads:[~2003-06-30 15:17 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-30 16:05 Richard Bland [this message]
2003-07-02 16:50 ` Hannu E K Nevalainen (garbage mail)
-- strict thread matches above, loose matches on Subject: below --
2003-07-08 14:12 Dean Scarff
2003-06-27 13:03 Richard Bland
2003-06-26 20:09 John Vincent
2003-06-26 16:42 Richard Bland
2003-06-26 12:29 Richard Bland
2003-06-26 16:21 ` Igor Pechtchanski
2003-06-30 13:31 ` Corinna Vinschen
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=F668F8488B0EA74D89C887A74FB4116F2BA730@Endor \
--to=r.bland@espo.org \
--cc=cygwin@cygwin.com \
/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).