From: Bruce Ashfield <bruce.ashfield@windriver.com>
To: <ulf@emagii.com>,
Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Cc: openembedded-core@openembedded.org
Subject: Re: Adding kernel patches using "git am"?
Date: Wed, 30 Nov 2011 14:07:22 -0500 [thread overview]
Message-ID: <4ED67EEA.4080800@windriver.com> (raw)
In-Reply-To: <4ED6070C.20904@emagii.com>
On 11-11-30 05:35 AM, Ulf Samuelsson wrote:
> Is there a reason for using "patch" instead of "git am" on let's say the
> kernel.
>
> If I want to do some modification, of the kernel, I can like Graeme
> description at
> http://www.slimlogic.co.uk/2011/05/openembeddedangstrom-kernel-workflow/ do
> bitbake -c configure virtual/kernel
>
> and then have an initialized git tree ready to be modified.
>
> "git am" is of course more sensitive to the patch quality than "patch"
> but that has some advantages as well.
Not answering the question directly, but if you use the linux-yocto
kernel and related infrastructure, patch is not used to apply changes
to the tree. It is done under the covers with guilt or git am applying
changes to the tree (along with other git operations for more complex
situations).
Cheers,
Bruce
>
> It also makes the recipe more complex at this stage.
>
> --
> Best Regards
> Ulf Samuelsson
> eMagii
>
>
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
prev parent reply other threads:[~2011-11-30 19:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-30 10:35 Adding kernel patches using "git am"? Ulf Samuelsson
2011-11-30 15:11 ` Chris Larson
2011-11-30 19:07 ` Bruce Ashfield [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=4ED67EEA.4080800@windriver.com \
--to=bruce.ashfield@windriver.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=openembedded-core@openembedded.org \
--cc=ulf@emagii.com \
/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