X-Recipient: archive-cygwin AT delorie DOT com
DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:subject:to:references:from:message-id:date
	:mime-version:in-reply-to:content-type; q=dns; s=default; b=g2Up
	K5AnaD9S1NYE6/4JnW3kPN5n2q80xcnSjAIYXU/j4Y/o4Ojncu9kyqouKFYaXT+Y
	cyrcylpjdx27AW7xOnbwVojGLdR71vfdMsLfdlNSOd/7ddALb2EFH8EDNfCkxPVp
	heK5W1Sm7QxL9AIGu4YnMR+9oUeZSlkfAdMqDks=
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:subject:to:references:from:message-id:date
	:mime-version:in-reply-to:content-type; s=default; bh=x/GfZNEn8O
	EJd++eC7rwRR3sMY8=; b=KBM/lPyflI6gGrej7q5pzU9QHUle++kro90LAPSidl
	70y2k/tI8grOi5KO97c6IHEfHlzBF75xtZCAVO74MY8K24XSf2UEI8NctOJ/6GYO
	De3FJNRHpEU0V2USzHe5kQpPgeqWVyDzzCJ134Eiu/kYLlb3/aFKzhfGKWsnkwit
	8=
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id: <cygwin.cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/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
Authentication-Results: sourceware.org; auth=none
X-Virus-Found: No
X-Spam-SWARE-Status: No, score=-1.9 required=5.0 tests=BAYES_00,SPF_HELO_PASS,T_RP_MATCHES_RCVD autolearn=ham version=3.3.2 spammy=Hx-languages-length:1314, dear, Dear, H*c:application
X-HELO: mx1.redhat.com
DMARC-Filter: OpenDMARC Filter v1.3.2 mx1.redhat.com 579F4C04B31F
Authentication-Results: ext-mx07.extmail.prod.ext.phx2.redhat.com; dmarc=none (p=none dis=none) header.from=redhat.com
Authentication-Results: ext-mx07.extmail.prod.ext.phx2.redhat.com; spf=pass smtp.mailfrom=eblake AT redhat DOT com
DKIM-Filter: OpenDKIM Filter v2.11.0 mx1.redhat.com 579F4C04B31F
Subject: Re: CR-LF handling behavior of SED changed recently - this breaks a lot of MinGW cross build scripts
To: cygwin AT cygwin DOT com, michael DOT soegtrop AT intel DOT com
References: <0F7D3B1B3C4B894D824F5B822E3E5A175B2636E4 AT IRSMSX103 DOT ger DOT corp DOT intel DOT com>
From: Eric Blake <eblake AT redhat DOT com>
Openpgp: url=http://people.redhat.com/eblake/eblake.gpg
Message-ID: <a53282b6-d00c-aad8-76a6-26b4089a9623@redhat.com>
Date: Wed, 7 Jun 2017 12:23:33 -0500
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.1.0
MIME-Version: 1.0
In-Reply-To: <0F7D3B1B3C4B894D824F5B822E3E5A175B2636E4@IRSMSX103.ger.corp.intel.com>
Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="2euMpSWrEreoAa18ipWkxomA0Mju36D70"
X-IsSubscribed: yes

--2euMpSWrEreoAa18ipWkxomA0Mju36D70
Content-Type: multipart/mixed; boundary="f1PXNDcf4twEwCM9e7r97KbhMVSmtGCBw";
 protected-headers="v1"
From: Eric Blake <eblake AT redhat DOT com>
To: cygwin AT cygwin DOT com, michael DOT soegtrop AT intel DOT com
Message-ID: <a53282b6-d00c-aad8-76a6-26b4089a9623 AT redhat DOT com>
Subject: Re: CR-LF handling behavior of SED changed recently - this breaks a
 lot of MinGW cross build scripts
References: <0F7D3B1B3C4B894D824F5B822E3E5A175B2636E4 AT IRSMSX103 DOT ger DOT corp DOT intel DOT com>
In-Reply-To: <0F7D3B1B3C4B894D824F5B822E3E5A175B2636E4 AT IRSMSX103 DOT ger DOT corp DOT intel DOT com>


--f1PXNDcf4twEwCM9e7r97KbhMVSmtGCBw
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: quoted-printable

On 06/07/2017 11:23 AM, Soegtrop, Michael wrote:
> Dear Cygwin Team,
>=20
> in the latest version of cygwin with sed-4.4-1.tar.bz2 the behavior of se=
d regarding handling CR-LF sequences changed.

And the change was documented (don't you read the release notes?)
https://cygwin.com/ml/cygwin-announce/2017-02/msg00036.html

> I would say that the documented behavior in both versions is that they re=
place CR-LF with LF,

No, the documented behavior is that CR-LF is converted to LF only for
text-mounted files; but pipelines are default binary-mounted.  If you
want to strip CR from a pipeline, then make it explicit.

> var=3D$( prog | sed .)

Rewrite that to var=3D$( prog | tr -d '\r' | sed .)

> Is this considered a bug in sed 4.4-1 or is the old behavior and the -b o=
ption considered deprecated and it was just forgotten to remove the documen=
tation for the -b option?

The -b option still works (forcing binary mode when you otherwise have a
text mount); what changed was that the default behavior of pipelines is
now binary instead of text, as binary is a better default mode for Linux
compatibility.

--=20
Eric Blake, Principal Software Engineer
Red Hat, Inc.           +1-919-301-3266
Virtualization:  qemu.org | libvirt.org


--f1PXNDcf4twEwCM9e7r97KbhMVSmtGCBw--

--2euMpSWrEreoAa18ipWkxomA0Mju36D70
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2
Comment: Public key at http://people.redhat.com/eblake/eblake.gpg
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQEcBAEBCAAGBQJZODaWAAoJEKeha0olJ0NqHf0H+wbKA9a5bxcrs/yL+S2Qi4vg
B0pXckQhVwo59Vh9MQamRb7b0UFTvZTANheKLfDLgJlBxYp5BPyODut54n8rfGuJ
0ikS0+r9XUqLPjdrICUMgPfTKjaVgGRwCow2OLmwqZy3CELksS9iS28hdT9sTwuO
aBSLCCklufQtffOwKPxuebAy0dSAp50o4k9fbGVkU55uitCW58Nsebeb+gitj+l6
EnCdapLpwx0KQ63nScRHWjDvC27UfRK4zfrKrL3erAw8woeZUPDt5SJpXfEW4F4j
g9BaQfoUaJHNCmv7W1skEENVgmDmBUatiJ2G0+H3IU7aq7Xb2GrJTEOcOJwWZFY=
=YeBW
-----END PGP SIGNATURE-----

--2euMpSWrEreoAa18ipWkxomA0Mju36D70--