From: Martin Jansa <martin.jansa@gmail.com>
To: openembedded-core@lists.openembedded.org
Subject: [PATCH 0/2] Packaging license texts in PN
Date: Thu, 17 Jan 2013 12:49:42 +0100 [thread overview]
Message-ID: <cover.1358423316.git.Martin.Jansa@gmail.com> (raw)
The following changes since commit 0ada16fe509d9a8608c05d16666243c8ebe4d3b3:
apmd: fix license segment md5sum boundary (2013-01-16 11:54:47 +0000)
are available in the git repository at:
git://git.openembedded.org/openembedded-core-contrib jansa/license-pn
http://cgit.openembedded.org/cgit.cgi/openembedded-core-contrib/log/?h=jansa/license-pn
Martin Jansa (2):
license.bbclass: extract functionality to find license files to
separate function
license.bbclass: package license texts to PN-lic when
LICENSE_CREATE_PACKAGE is enabled
meta/classes/license.bbclass | 78 ++++++++++++++++++++++++++++++++++----------
1 file changed, 60 insertions(+), 18 deletions(-)
--
1.8.1.1
next reply other threads:[~2013-01-17 12:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-17 11:49 Martin Jansa [this message]
2013-01-17 11:49 ` [PATCH 1/2] license.bbclass: extract functionality to find license files to separate function Martin Jansa
2013-01-17 11:49 ` [PATCH 2/2] license.bbclass: package license texts to PN-lic when LICENSE_CREATE_PACKAGE is enabled Martin Jansa
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.1358423316.git.Martin.Jansa@gmail.com \
--to=martin.jansa@gmail.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