From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] barebox: add support for custom version, tarball, git and patch dir
Date: Thu, 22 Sep 2011 20:57:59 +0200 [thread overview]
Message-ID: <20110922205759.01de08f3@skate> (raw)
In-Reply-To: <201109221920.37170.arnout@mind.be>
Le Thu, 22 Sep 2011 19:20:36 +0200,
Arnout Vandecappelle <arnout@mind.be> a ?crit :
> 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.
I typically make a per-project branch as well, but for kernel/u-boot
patches, I typically like to store them into
board/<company>/<project>/linux-x.y.z-patches
board/<company>/<project>/uboot-x.y.z-patches
because those patches are typically board and project specific.
Where do you put them ? Directly in linux/ and boot/uboot/ ?
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2011-09-22 18:57 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 [this message]
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=20110922205759.01de08f3@skate \
--to=thomas.petazzoni@free-electrons.com \
--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