From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] busybox: rename patches as per the new standard and update 1.21.0 mdev
Date: Tue, 23 Apr 2013 23:42:05 +0200 [thread overview]
Message-ID: <87bo94divm.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <5176F8B6.8020204@mind.be> (Arnout Vandecappelle's message of "Tue, 23 Apr 2013 23:10:14 +0200")
>>>>> "Arnout" == Arnout Vandecappelle <arnout@mind.be> writes:
Arnout> On 23/04/13 16:04, Peter Korsgaard wrote:
>>>>>>> "Gustavo" == Gustavo Zacarias <gustavo@zacarias.com.ar> writes:
>>
Gustavo> Rename patches as per the patch naming policy and update the
Gustavo> mdev fix patch for 1.21.0 which reinstates subsystem matching
Gustavo> functionality.
>>
>> Sorry, I disagree with this rename. I know this is what we discussed at
>> the dev day, but it imho makes more sense to use the upstream naming
>> convention for busybox:
>>
>> http://busybox.net/downloads/fixes-1.21.0/
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).
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2013-04-23 21:42 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 [this message]
2013-04-24 6:07 ` Gustavo Zacarias
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=87bo94divm.fsf@dell.be.48ers.dk \
--to=jacmet@uclibc.org \
--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.