From: "João Henrique Ferreira de Freitas" <joaohf@gmail.com>
To: openembedded-core@lists.openembedded.org
Cc: dvhart@linux.intel.com
Subject: [PATCH v2 0/2] Add task to create kernel config fragments
Date: Sun, 16 Feb 2014 18:40:56 -0300 [thread overview]
Message-ID: <1392586858-12205-1-git-send-email-joaohf@gmail.com> (raw)
Changes in v2:
- address Darren
- task name, using diffconfig
- except on failure
- space after ','
- printing the path to fragment
- address RP's comments (import os)
Hi,
These patches add a new task called fragmentconfig which should be used
when the user need to extract a diff between two kernel config files.
For instance:
bitbake -c menuconfig linux-yoco
[do some changes and save]
bitbake -c fragmentconfig linux-yocto
See the fragment.cfg in $WORKDIR/fragment.cfg
This closes [YOCTO #3862]
Thanks.
João Henrique Ferreira de Freitas (2):
kernel-yocto: Add do_diffconfig task
cml1.bbclass: Add diffconfig task to cml1
meta/classes/cml1.bbclass | 33 +++++++++++++++++++++++++++++++++
meta/classes/kernel-yocto.bbclass | 2 ++
2 files changed, 35 insertions(+)
--
1.8.3.2
next reply other threads:[~2014-02-16 21:41 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-16 21:40 João Henrique Ferreira de Freitas [this message]
2014-02-16 21:40 ` [PATCH v2 1/2] kernel-yocto: Add do_diffconfig task João Henrique Ferreira de Freitas
2014-02-18 17:54 ` Darren Hart
2014-02-16 21:40 ` [PATCH v2 2/2] cml1.bbclass: Add diffconfig task to cml1 João Henrique Ferreira de Freitas
2014-02-18 17:54 ` Darren Hart
2014-02-17 13:38 ` [PATCH v2 0/2] Add task to create kernel config fragments Otavio Salvador
2014-02-17 14:22 ` João Henrique Freitas
2014-02-17 14:43 ` Otavio Salvador
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=1392586858-12205-1-git-send-email-joaohf@gmail.com \
--to=joaohf@gmail.com \
--cc=dvhart@linux.intel.com \
--cc=openembedded-core@lists.openembedded.org \
/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