From: Gustavo Zacarias <gustavo@zacarias.com.ar>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] busybox: rename patches as per the new standard and update 1.21.0 mdev
Date: Wed, 24 Apr 2013 03:07:13 -0300 [thread overview]
Message-ID: <51777691.2020702@zacarias.com.ar> (raw)
In-Reply-To: <87bo94divm.fsf@dell.be.48ers.dk>
On 04/23/2013 06:42 PM, Peter Korsgaard wrote:
> Arnout> Actually, if upstream has the patches available for download,
> Arnout> they should be downloaded instead of of included in buildroot,
> Arnout> no?
>
> True. For busybox our patch download infrastructure unfortunately
> doesn't work as the patches aren't located in the same directory as the
> tarball (and the fact that we support multiple versions also makes it a
> bit more complicated).
The problem with downloading busybox patches directly is that upstream
kind of sucks regarding naming and updates.
For instance the mdev patch changed without being reflected in the
filename, and so did other patches in the past.
This could cause unexpected behaviour depending on which patch each user
got, specially when they're being early adopters of new versions and
using a common download directory.
Telling people to "remove your patches to force a new download and try
again" would just be adding unnecessary noise/bugs.
Regards.
next prev parent reply other threads:[~2013-04-24 6:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-23 13:21 [Buildroot] [PATCH] busybox: rename patches as per the new standard and update 1.21.0 mdev Gustavo Zacarias
2013-04-23 14:04 ` Peter Korsgaard
2013-04-23 14:15 ` Gustavo Zacarias
2013-04-23 21:10 ` Arnout Vandecappelle
2013-04-23 21:42 ` Peter Korsgaard
2013-04-24 6:07 ` Gustavo Zacarias [this message]
2013-04-24 6:11 ` 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=51777691.2020702@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 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.