From: David Macek <david.macek.0@gmail.com>
To: cygwin@cygwin.com
Subject: Re: when using cygwin version 2.8.2 the behavior of CR/LF changed completely compared to previous versions
Date: Wed, 02 Aug 2017 15:46:00 -0000 [thread overview]
Message-ID: <860bf833-674f-1e8c-4165-35e36376480e@gmail.com> (raw)
In-Reply-To: <DB6PR0601MB20851310E2DD3EF70CEF38B5BAB00@DB6PR0601MB2085.eurprd06.prod.outlook.com>
[-- Attachment #1: Type: text/plain, Size: 576 bytes --]
On 2. 8. 2017 17:34, Roger Krebs wrote:
> Hi,
>
> after updating from version 1.7.33 to version 2.8.2 the behavior of CR-LF handling completely changed. This results in several srcipt errors etc.
See announcements:
* <https://cygwin.com/ml/cygwin-announce/2017-02/msg00036.html> for sed
* <https://cygwin.com/ml/cygwin-announce/2017-02/msg00035.html> for grep
* <https://cygwin.com/ml/cygwin-announce/2017-02/msg00034.html> for gawk
There was also a discussion about these changes at <https://cygwin.com/ml/cygwin/2017-06/msg00040.html>.
--
David Macek
[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 3715 bytes --]
next prev parent reply other threads:[~2017-08-02 15:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-02 15:34 Roger Krebs
2017-08-02 15:46 ` David Macek [this message]
2017-08-03 12:47 ` AW: " Roger Krebs
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=860bf833-674f-1e8c-4165-35e36376480e@gmail.com \
--to=david.macek.0@gmail.com \
--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).