From: Ulf Samuelsson <openembedded-core@emagii.com>
To: openembedded-core@openembedded.org
Subject: Adding kernel patches using "git am"?
Date: Wed, 30 Nov 2011 11:35:56 +0100 [thread overview]
Message-ID: <4ED6070C.20904@emagii.com> (raw)
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.
It also makes the recipe more complex at this stage.
--
Best Regards
Ulf Samuelsson
eMagii
next reply other threads:[~2011-11-30 11:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-30 10:35 Ulf Samuelsson [this message]
2011-11-30 15:11 ` Adding kernel patches using "git am"? Chris Larson
2011-11-30 19:07 ` Bruce Ashfield
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=4ED6070C.20904@emagii.com \
--to=openembedded-core@emagii.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