From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] barebox: add support for custom version, tarball, git and patch dir
Date: Thu, 22 Sep 2011 19:20:36 +0200 [thread overview]
Message-ID: <201109221920.37170.arnout@mind.be> (raw)
In-Reply-To: <1316290988-25108-1-git-send-email-plagnioj@jcrosoft.com>
On Saturday 17 September 2011 22:23:08, Jean-Christophe PLAGNIOL-VILLARD
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
Do people often use buildroot this way? I always make a project-specific
branch of the buildroot tree and drop any patches directly in there.
Not that it hurts to have the option of course :-)
But if many people use buildroot this way, it would make total sense to try
to implement overlays like openembedded does.
Regards,
Arnout
--
Arnout Vandecappelle arnout at mind be
Senior Embedded Software Architect +32-16-286540
Essensium/Mind http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint: 31BB CF53 8660 6F88 345D 54CC A836 5879 20D7 CF43
next prev parent reply other threads:[~2011-09-22 17:20 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 [this message]
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
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=201109221920.37170.arnout@mind.be \
--to=arnout@mind.be \
--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.