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 16:15:46 +0100 [thread overview]
Message-ID: <87hc48o6hp.fsf@macbook.be.48ers.dk> (raw)
In-Reply-To: <200901091608.17923.markus.heidelberg@web.de> (Markus Heidelberg's message of "Fri\, 9 Jan 2009 16\:08\:17 +0100")
>>>>> "Markus" == Markus Heidelberg <markus.heidelberg@web.de> writes:
>> (E.G. Linux/U-Boot). Building upstream versions of those rarely make
>> sense for custom boards, so having the option to apply custom patches
Markus> Which is available, but only in addition to the general patches lying
Markus> around.
Exactly, it should ofcourse be INSTEAD.
>> 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.
Markus> I just had a look at it. Some sort of checking for newer commits and
Markus> then updating the cloned tree would be nice.
Yes, indeed.
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2009-01-09 15:15 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
2009-01-09 15:08 ` Markus Heidelberg
2009-01-09 15:15 ` Peter Korsgaard [this message]
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=87hc48o6hp.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