From: Saul Wold <sgw@linux.intel.com>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 0/1] archiver.bbclass: Reduce some duplication for function get_licenses
Date: Tue, 12 Jun 2012 11:07:08 -0700 [thread overview]
Message-ID: <4FD7854C.6030204@linux.intel.com> (raw)
In-Reply-To: <cover.1339034063.git.xiaofeng.yan@windriver.com>
On 06/06/2012 07:01 PM, xiaofeng.yan@windriver.com wrote:
> From: Xiaofeng Yan<xiaofeng.yan@windriver.com>
>
> The content to modify this bbclass is as follow:
> - Use the existing functions to get license as a directory instead of
> rewriting it for avoiding code duplication.
> - Use SPDXLICENSEMAP to map licenses
>
> The following changes since commit df8f55a919b3cc602ce1f1c51630c7edf6e36b55:
> Cristian Iorga (1):
> ltp: Add patch to correct failing build
>
> are available in the git repository at:
>
> git://git.pokylinux.org/poky-contrib xiaofeng/2473
> http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=xiaofeng/2473
>
> Xiaofeng Yan (1):
> archiver.bbclass: Reduce some duplication for function get_licenses
>
> meta/classes/archiver.bbclass | 23 ++++++++++++-----------
> 1 files changed, 12 insertions(+), 11 deletions(-)
>
>
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
>
>
Merged into OE-Core
Thanks
Sau!
prev parent reply other threads:[~2012-06-12 18:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-07 2:01 [PATCH 0/1] archiver.bbclass: Reduce some duplication for function get_licenses xiaofeng.yan
2012-06-07 2:01 ` [PATCH 1/1] " xiaofeng.yan
2012-06-12 18:07 ` Saul Wold [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=4FD7854C.6030204@linux.intel.com \
--to=sgw@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