From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] u-boot: add config option to disable general patches
Date: Fri, 09 Jan 2009 11:54:29 +0100 [thread overview]
Message-ID: <87y6xkpx5m.fsf@macbook.be.48ers.dk> (raw)
In-Reply-To: <200901081917.16406.markus.heidelberg@web.de> (Markus Heidelberg's message of "Thu\, 8 Jan 2009 19\:17\:16 +0100")
>>>>> "Markus" == Markus Heidelberg <markus.heidelberg@web.de> writes:
Hi,
Markus> It's the same as with the Linux kernel: you wouldn't like
Markus> patches lying around in Buildroot, which you can't disable
Markus> and always get applied.
I've been pondering about adding a bit of flexibility to the packages
that often need platform specific handling
(E.G. Linux/U-Boot). Building upstream versions of those rarely make
sense for custom boards, so having the option to apply custom patches
or grabbing the entire tree from other version control system seems
sensible.
Grant Likely once sent a patch series adding support for using other
git trees to the kernel build, that I still need to look into.
>> The number of configuration options we have in target/u-boot nowadays
>> is getty silly.
Markus> That's right, but this option is not one to be passed to
Markus> U-Boot like all this board specific stuff currently in
Markus> Config.in.
True.
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2009-01-09 10:54 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-14 7:54 [Buildroot] [PATCH] u-boot: add config option to disable patching Markus Heidelberg
2008-11-14 13:37 ` Peter Korsgaard
2008-11-15 10:56 ` Markus Heidelberg
2009-01-08 14:10 ` [Buildroot] [PATCH] u-boot: add config option to disable general patches Markus Heidelberg
2009-01-08 14:33 ` Peter Korsgaard
2009-01-08 18:17 ` Markus Heidelberg
2009-01-09 10:54 ` Peter Korsgaard [this message]
2009-01-09 15:08 ` Markus Heidelberg
2009-01-09 15:15 ` Peter Korsgaard
2009-01-09 16:07 ` Markus Heidelberg
2009-01-08 21:56 ` Ulf Samuelsson
2009-01-09 11:07 ` Thomas Lundquist
2009-01-09 11:26 ` 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=87y6xkpx5m.fsf@macbook.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox