From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by yocto-www.yoctoproject.org (Postfix, from userid 118) id CAC1EE00D4A; Tue, 25 Jun 2019 17:15:23 -0700 (PDT) X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on yocto-www.yoctoproject.org X-Spam-Level: X-Spam-Status: No, score=-6.9 required=5.0 tests=BAYES_00,HTML_MESSAGE, RCVD_IN_DNSWL_HI autolearn=ham version=3.3.1 X-Spam-HAM-Report: * -1.9 BAYES_00 BODY: Bayes spam probability is 0 to 1% * [score: 0.0000] * -5.0 RCVD_IN_DNSWL_HI RBL: Sender listed at https://www.dnswl.org/, high * trust * [156.147.23.53 listed in list.dnswl.org] * 0.0 HTML_MESSAGE BODY: HTML included in message Received: from lgeamrelo11.lge.com (lgeamrelo13.lge.com [156.147.23.53]) by yocto-www.yoctoproject.org (Postfix) with ESMTP id 5D439E00A7D for ; Tue, 25 Jun 2019 17:15:21 -0700 (PDT) Received: from unknown (HELO lgemrelse6q.lge.com) (156.147.1.121) by 156.147.23.53 with ESMTP; 26 Jun 2019 09:15:20 +0900 X-Original-SENDERIP: 156.147.1.121 X-Original-MAILFROM: keith.derrick@lge.com Received: from unknown (HELO LGSVL-EXC02.lgsvl.net) (10.195.253.63) by 156.147.1.121 with ESMTP; 26 Jun 2019 09:15:19 +0900 X-Original-SENDERIP: 10.195.253.63 X-Original-MAILFROM: keith.derrick@lge.com Received: from LGSVL-EXC01.lgsvl.net (10.195.253.62) by LGSVL-EXC02.lgsvl.net (10.195.253.63) with Microsoft SMTP Server (TLS) id 15.0.1044.25; Tue, 25 Jun 2019 17:15:18 -0700 Received: from LGSVL-EXC01.lgsvl.net ([10.195.253.62]) by LGSVL-EXC01.lgsvl.net ([10.195.253.62]) with mapi id 15.00.1044.021; Tue, 25 Jun 2019 17:15:18 -0700 From: keith.derrick To: Martin Jansa Thread-Topic: [yocto] Dealing with line endings Thread-Index: AQHVKv0I55jwuTmvf0+1TpLuHZmyKaasbvsAgACjbo4= Date: Wed, 26 Jun 2019 00:15:17 +0000 Message-ID: <1561508118148.84601@lge.com> References: <1561429587556.6733@lge.com>, In-Reply-To: Accept-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-ms-exchange-transport-fromentityheader: Hosted x-originating-ip: [10.195.247.37] MIME-Version: 1.0 Cc: "yocto@yoctoproject.org" Subject: Re: Dealing with line endings X-BeenThere: yocto@yoctoproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Discussion of all things Yocto Project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 26 Jun 2019 00:15:23 -0000 Content-Language: en-US Content-Type: multipart/alternative; boundary="_000_156150811814884601lgecom_" --_000_156150811814884601lgecom_ Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Thanks Martin, that fixed it nicely. ________________________________ From: Martin Jansa Sent: Tuesday, June 25, 2019 12:30 AM To: Keith Derrick/LGEUS Advanced Platform(keith.derrick@lge.com) Cc: yocto@yoctoproject.org Subject: Re: [yocto] Dealing with line endings Hi Keith, you can use dos2unix.bbclass: http://git.openembedded.org/openembedded-core/tree/meta/classes/dos2unix.bb= class to convert them before do_patch. Cheers, On Tue, Jun 25, 2019 at 4:57 AM keith.derrick > wrote: I am using an upstream repo with a mix of line endings. In my recipe, I'm applying a patch with normalized line endings, as our met= a layer repo has a .gitattributes with "text=3Dauto" set. The patch is failing due to "different line endings". Can the git fetcher be configured to normalize line endings on unpack? I tr= ied setting core.autocrlf in my global .gitconfig, but the fetcher/unpacker= seems to ignore it. Thanks Keith -- _______________________________________________ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto --_000_156150811814884601lgecom_ Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable

Thanks Martin, that fixed it nicely.

From: Martin Jansa <mart= in.jansa@gmail.com>
Sent: Tuesday, June 25, 2019 12:30 AM
To: Keith Derrick/LGEUS Advanced Platform(keith.derrick@lge.com)
Cc: yocto@yoctoproject.org
Subject: Re: [yocto] Dealing with line endings
 
Hi Keith,

you can use dos2unix.bbclass:
to convert them before do_patch.

Cheers,

On Tue, Jun 25, 2019 at 4:57 AM keith= .derrick <keith.derrick@lge.com= > wrote:

I am using an upstream repo with a mix of line endings.


In my recipe, I'm applying a patch with normalized line endings, as our = meta layer repo has a .gitattributes with "text=3Dauto" set.


The patch is failing due to "different line endings".


Can the git fetcher be configured to normalize line endings on unpack? I= tried setting core.autocrlf in my global .gitconfig, but the fetcher/unpac= ker seems to ignore it.


Thanks

Keith


--
_______________________________________________
yocto mailing list
yocto@yoctoproj= ect.org
https://lists.yoctoproject.org/listinfo/yocto
--_000_156150811814884601lgecom_--