DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:from:to:subject:date:message-id:references
	:in-reply-to:content-type:content-transfer-encoding
	:mime-version; q=dns; s=default; b=HLZ+WoItuKBXEvvJ7cmNbz0U0EKCM
	sXse0WjVQ5WiVVhYECVmP92X4KZjUl3p5x/OHS2LRNg77pOYe4KzWxmJt1LT+RC5
	QNuQVkQtvLBoJhR/b1j5G21pdeiiCXrx50Y43AtoqqLXzKvfWis7xHpJ1F+vYIeZ
	3rwGF4Mcvo1a+s=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
From: Roger Krebs <Roger.Krebs@stage-entertainment.com>
To: David Macek <david.macek.0@gmail.com>,
        "cygwin@cygwin.com"	<cygwin@cygwin.com>
Subject: AW: when using cygwin version 2.8.2 the behavior of CR/LF changed completely compared to previous versions
Date: Thu, 3 Aug 2017 12:47:02 +0000
Message-ID: <DB6PR0601MB2085AF3A70102475ABB9B0A5BAB10@DB6PR0601MB2085.eurprd06.prod.outlook.com>
References: <DB6PR0601MB20851310E2DD3EF70CEF38B5BAB00@DB6PR0601MB2085.eurprd06.prod.outlook.com> <860bf833-674f-1e8c-4165-35e36376480e@gmail.com>
In-Reply-To: <860bf833-674f-1e8c-4165-35e36376480e@gmail.com>
received-spf: None (protection.outlook.com: stage-entertainment.com does not designate permitted sender hosts)
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-originalarrivaltime: 03 Aug 2017 12:47:02.2981 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: e51757a1-30a6-4313-99f1-91a899d67e0c
X-MS-Exchange-Transport-CrossTenantHeadersStamped: DB6PR0601MB2085
X-IsSubscribed: yes
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from base64 to 8bit by delorie.com id v73ClQ1P021647

Hi,

I've seen that there were some changes regarding CR/LLF in sed and cygcheck, but I havn't recognized that several other tool has also changed their behavior in the past. We haven't done an update for a longer period of time (why update when anything runs well) and therefor now we've been faced with several similar changes in the behavior of different tools. That's the reason why we've thought that this must be something general.

Many thanks to bring me into the right context. We've made some smaller changes in our scripts and everything seems to work fine now.

Again many thanks for the very quick and helpful response.

Best Regards
Roger Krebs

-----Ursprüngliche Nachricht-----
Von: cygwin-owner@cygwin.com [mailto:cygwin-owner@cygwin.com] Im Auftrag von David Macek
Gesendet: Mittwoch, 2. August 2017 17:46
An: cygwin@cygwin.com
Betreff: Re: when using cygwin version 2.8.2 the behavior of CR/LF changed completely compared to previous versions

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


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