From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 11931] Bugs in support/scripts/apply-patches.sh
Date: Thu, 15 Aug 2019 13:25:34 +0000 [thread overview]
Message-ID: <bug-11931-163-6w9qWyN0nz@https.bugs.busybox.net/> (raw)
In-Reply-To: <bug-11931-163@https.bugs.busybox.net/>
https://bugs.busybox.net/show_bug.cgi?id=11931
--- Comment #1 from Thomas Petazzoni <thomas.petazzoni@free-electrons.com> ---
Thanks for the bug report! We do not want to rely on the patch version though.
Indeed, what if someone that has a patch > = 2.7 on his machine adds a patch
using renames to Buildroot, which gets committed, and then this Buildroot gets
used by someone having a patch < 2.7 on his machine ? The build will break. So
clearly, we should not make it behave differently depending on the patch
version.
The uncompression part is correct though. Would you mind submitting it as a
proper patch to the Buildroot mailing list, with a commit log and
Signed-off-by, so that we can apply it ? Thanks!
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2019-08-15 13:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-04 8:20 [Buildroot] [Bug 11931] New: Bugs in support/scripts/apply-patches.sh bugzilla at busybox.net
2019-08-15 13:25 ` bugzilla at busybox.net [this message]
2020-10-17 12:45 ` [Buildroot] [Bug 11931] " bugzilla at busybox.net
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=bug-11931-163-6w9qWyN0nz@https.bugs.busybox.net/ \
--to=bugzilla@busybox.net \
--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 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.