From: Saul Wold <sgw@linux.intel.com>
To: openembedded-core@lists.openembedded.org
Subject: [PATCH 0/2] non-GPLv3 fixes
Date: Thu, 5 Jan 2012 10:38:35 -0800 [thread overview]
Message-ID: <cover.1325788605.git.sgw@linux.intel.com> (raw)
Richard,
Better commit messages.
These fixes are for the non-GPLv3 build
Sau!
The following changes since commit 563828bad19a242bba9ce3db461bb5807037dfdf:
multilib: Abstract class extension code into classextend.py (2012-01-05 12:36:08 +0000)
are available in the git repository at:
git://git.openembedded.org/openembedded-core-contrib sgw/fix
http://cgit.openembedded.org/cgit.cgi/openembedded-core-contrib/log/?h=sgw/fix
Saul Wold (2):
util-linux: Update patch for non-GPLv3
gnutls: remove gettext patch for non-GPLv3
.../util-linux-2.20.1/remove-lscpu.patch | 94 +------------------
meta/recipes-support/gnutls/gnutls_2.12.14.bb | 13 ++-
2 files changed, 15 insertions(+), 92 deletions(-)
--
1.7.6.4
next reply other threads:[~2012-01-05 18:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-05 18:38 Saul Wold [this message]
2012-01-05 18:38 ` [PATCH 1/2] util-linux: Update patch for non-GPLv3 Saul Wold
2012-01-05 18:38 ` [PATCH 2/2] gnutls: remove gettext " Saul Wold
2012-01-05 19:33 ` Denys Dmytriyenko
2012-01-09 5:30 ` 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.1325788605.git.sgw@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