From: Elizabeth Flanagan <elizabeth.flanagan@intel.com>
To: oe-core <openembedded-core@lists.openembedded.org>
Subject: [PATCH 0/1] Correcting LICENSE for ossp-uuid
Date: Tue, 25 Sep 2012 15:31:59 -0700 [thread overview]
Message-ID: <cover.1348612198.git.elizabeth.flanagan@intel.com> (raw)
LICENSE information for ossp-uuid was tossing a warning. this fixes license
as well as provides a more detailed LIC_FILES_CHKSUM.
The following changes since commit a8edf79fce381d0433f18bd38df6cd74008e5179:
bitbake: fetch2/git: Don't use deprecated API (2012-09-25 15:55:57 +0100)
are available in the git repository at:
git://git.yoctoproject.org/poky-contrib eflanagan/ossp-uuid-native
http://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=eflanagan/ossp-uuid-native
Elizabeth Flanagan (1):
ossp-uuid: LICENSE type corrections.
meta/recipes-devtools/ossp-uuid/ossp-uuid_1.6.2.bb | 7 ++++---
1 files changed, 4 insertions(+), 3 deletions(-)
--
1.7.5.4
next reply other threads:[~2012-09-25 22:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-25 22:31 Elizabeth Flanagan [this message]
2012-09-25 22:32 ` [PATCH 1/1] ossp-uuid: LICENSE type corrections Elizabeth Flanagan
2012-09-27 15:50 ` [PATCH 0/1] Correcting LICENSE for ossp-uuid 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.1348612198.git.elizabeth.flanagan@intel.com \
--to=elizabeth.flanagan@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