From: Gustavo Zacarias <gustavo@zacarias.com.ar>
To: buildroot@busybox.net
Subject: [Buildroot] build error since a change in apply-patches.sh
Date: Mon, 16 Sep 2013 07:40:36 -0300 [thread overview]
Message-ID: <5236E024.3030207@zacarias.com.ar> (raw)
In-Reply-To: <87y56xgkle.fsf@dell.be.48ers.dk>
On 09/16/2013 06:51 AM, Peter Korsgaard wrote:
> Yes, I already brough this up here:
>
> http://lists.busybox.net/pipermail/buildroot/2013-September/078292.html
>
> I guess the best option is just to go back to warn on non-patches.
Another headsup with apply-patches.sh:
There's an unintented side-effect of
5871b791995ebe295db7dca608afe3f293ce8953 too, it may apply patches that
are no longer necessary automatically via reverse (-R).
We may see unintended unfixing of things with this, i've seen it happen
to me with some yet unreleased fixes (the big automake bump).
Maybe adding a -N to patch would be in order?
Regards.
next prev parent reply other threads:[~2013-09-16 10:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-16 9:34 [Buildroot] build error since a change in apply-patches.sh Sagaert Johan
2013-09-16 9:51 ` Peter Korsgaard
2013-09-16 10:40 ` Gustavo Zacarias [this message]
2013-09-16 10:48 ` Peter Korsgaard
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=5236E024.3030207@zacarias.com.ar \
--to=gustavo@zacarias.com.ar \
--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