From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Where do I place patches for my local buildroot?
Date: Thu, 23 May 2013 18:39:21 +0200 [thread overview]
Message-ID: <20130523183921.6682d295@skate> (raw)
In-Reply-To: <0855BDD4CF82174A8BE362DE9F27C3BF01E3FEC82D33@pche-exchange>
Dear Morten Kvistgaard,
On Thu, 23 May 2013 17:05:03 +0200, Morten Kvistgaard wrote:
> I'd like to follow this buildroot concept of "patches". Eg. if I have
> a patch for a package, I place it in the package folder. If I have a
> patch for my linux kernel, I place it in the folder specified by the
> menuconfig. But suppose I have a patch for my Buildroot? Where do I
> place that?
>
> My current buildroot patch is for "packages/Config.in". (I'm adding
> some of my local packages and so I need to modify the Config.in.) I
> can also imagine other buildroot files, that I want to patch though.
> And if I place them as separate "patches" it'll be easier to upgrade
> ^^
The general recommendation is to create a git branch, and commit your
changes in there.
When a new Buildroot version is released, either rebase your branch on
top of the new Git tag, or merge the new Git tag into your branch.
> Btw, I can see in the maillist that there's supposed to be a "Local
> Packages" in the menuconfig? Is this so? I can't seem to find it.
> (I'm using buildroot 2013.02.)
Can you point the specific e-mail you're referring to?
Thanks!
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
prev parent reply other threads:[~2013-05-23 16:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-23 15:05 [Buildroot] Where do I place patches for my local buildroot? Morten Kvistgaard
2013-05-23 16:39 ` Thomas Petazzoni [this message]
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=20130523183921.6682d295@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