From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] barebox: add support for custom version, tarball, git and patch dir
Date: Thu, 22 Sep 2011 21:55:27 +0200 [thread overview]
Message-ID: <87d3es1he8.fsf@macbook.be.48ers.dk> (raw)
In-Reply-To: <201109221920.37170.arnout@mind.be> (Arnout Vandecappelle's message of "Thu, 22 Sep 2011 19:20:36 +0200")
>>>>> "Arnout" == Arnout Vandecappelle <arnout@mind.be> writes:
Arnout> On Saturday 17 September 2011 22:23:08, Jean-Christophe PLAGNIOL-VILLARD
Arnout> wrote:
>> +config BR2_TARGET_BAREBOX_CUSTOM_PATCH_DIR
>> + string "custom patch dir"
>> + help
>> + If your board requires custom patches, add the path to the
>> + directory containing the patches here. The patches must be
>> + named barebox-<version>-<something>.patch.
>> +
>> + Most users may leave this empty
Arnout> Do people often use buildroot this way? I always make a
Arnout> project-specific branch of the buildroot tree and drop any
Arnout> patches directly in there.
I need to support a bunch of projects at work, so I keep them all in a
seperate repo (which gets synced with mainline buildroot ever so
often. Bootloader and kernel are likewise in (shared) local repos.
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2011-09-22 19:55 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-17 20:23 [Buildroot] [PATCH] barebox: add support for custom version, tarball, git and patch dir Jean-Christophe PLAGNIOL-VILLARD
2011-09-18 20:06 ` Peter Korsgaard
2011-09-22 17:20 ` Arnout Vandecappelle
2011-09-22 18:57 ` Thomas Petazzoni
2011-09-22 19:45 ` Arnout Vandecappelle
2011-09-23 7:49 ` Thomas Petazzoni
2011-09-22 19:55 ` Peter Korsgaard [this message]
2011-09-23 6:27 ` Thomas De Schampheleire
2011-09-23 7:55 ` Thomas Petazzoni
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=87d3es1he8.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 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.