From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [git commit] qextserialport: fix line endings in patch 0002
Date: Sat, 26 Nov 2016 15:04:25 +0100 [thread overview]
Message-ID: <20161126150425.6084a4e3@free-electrons.com> (raw)
In-Reply-To: <24560a5e-b297-7406-e3ba-e9b1a933922b@mind.be>
Hello,
On Sat, 26 Nov 2016 11:48:57 +0100, Arnout Vandecappelle wrote:
> Didn't I warn about this in the commit message?
Yes, you did. I saw it the first time I looked at the patch, but then
forgot when actually applying later in the day. Which is why I fixed it
afterwards.
> To avoid this kind of problem in the future, perhaps we should add
> --ignore-whitespace to our patch calls?
You mean when applying the patches? Apparently, git am takes a
--ignore-space-change option, could be worth trying next time.
Thanks!
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
next prev parent reply other threads:[~2016-11-26 14:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-25 21:40 [Buildroot] [git commit] qextserialport: fix line endings in patch 0002 Thomas Petazzoni
2016-11-26 10:48 ` Arnout Vandecappelle
2016-11-26 14:04 ` Thomas Petazzoni [this message]
2016-11-26 15:12 ` Arnout Vandecappelle
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=20161126150425.6084a4e3@free-electrons.com \
--to=thomas.petazzoni@free-electrons.com \
--cc=buildroot@busybox.net \
/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