All of lore.kernel.org
 help / color / mirror / Atom feed
From: keith.derrick <keith.derrick@lge.com>
To: Martin Jansa <martin.jansa@gmail.com>
Cc: "yocto@yoctoproject.org" <yocto@yoctoproject.org>
Subject: Re: Dealing with line endings
Date: Wed, 26 Jun 2019 00:15:17 +0000	[thread overview]
Message-ID: <1561508118148.84601@lge.com> (raw)
In-Reply-To: <CA+chaQf7VB36-ihmnx+ARiJ7VC4rQcuBSHgmwj33ytr_fauERw@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1213 bytes --]

Thanks Martin, that fixed it nicely.

________________________________
From: Martin Jansa <martin.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:
http://git.openembedded.org/openembedded-core/tree/meta/classes/dos2unix.bbclass
to convert them before do_patch.

Cheers,

On Tue, Jun 25, 2019 at 4:57 AM keith.derrick <keith.derrick@lge.com<mailto: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=auto" 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/unpacker seems to ignore it.


Thanks

Keith


--
_______________________________________________
yocto mailing list
yocto@yoctoproject.org<mailto:yocto@yoctoproject.org>
https://lists.yoctoproject.org/listinfo/yocto

[-- Attachment #2: Type: text/html, Size: 2742 bytes --]

      reply	other threads:[~2019-06-26  0:15 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-25  2:26 Dealing with line endings keith.derrick
2019-06-25  7:30 ` Martin Jansa
2019-06-26  0:15   ` keith.derrick [this message]

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=1561508118148.84601@lge.com \
    --to=keith.derrick@lge.com \
    --cc=martin.jansa@gmail.com \
    --cc=yocto@yoctoproject.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.