From: <xiaofeng.yan@windriver.com>
To: <openembedded-core@lists.openembedded.org>
Subject: [PATCH 0/1] archiver.bbclass: Reduce some duplication for function get_licenses
Date: Thu, 7 Jun 2012 10:01:54 +0800 [thread overview]
Message-ID: <cover.1339034063.git.xiaofeng.yan@windriver.com> (raw)
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(-)
next reply other threads:[~2012-06-07 2:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-07 2:01 xiaofeng.yan [this message]
2012-06-07 2:01 ` [PATCH 1/1] archiver.bbclass: Reduce some duplication for function get_licenses xiaofeng.yan
2012-06-12 18:07 ` [PATCH 0/1] " Saul Wold
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=cover.1339034063.git.xiaofeng.yan@windriver.com \
--to=xiaofeng.yan@windriver.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