From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: openembedded-core@lists.openembedded.org
Subject: [PATCH 0/2] A couple of recipetool fixes
Date: Mon, 25 Jul 2016 20:47:16 +1200 [thread overview]
Message-ID: <cover.1469436396.git.paul.eggleton@linux.intel.com> (raw)
One bug fix and one improvement for recipetool.
The following changes since commit 0a2df616a5c3316704742f1dcf37b450920e0280:
boost: fix CVE-2012-2677 (2016-07-21 07:45:01 +0100)
are available in the git repository at:
git://git.openembedded.org/openembedded-core-contrib paule/recipetool-fixes4
http://cgit.openembedded.org/cgit.cgi/openembedded-core-contrib/log/?h=paule/recipetool-fixes4
Paul Eggleton (2):
lib/oe/recipeutils: fix patch_recipe*() with empty input
recipetool: record unknown license files
meta/lib/oe/recipeutils.py | 2 +-
scripts/lib/recipetool/create.py | 10 ++++++++++
2 files changed, 11 insertions(+), 1 deletion(-)
--
2.5.5
next reply other threads:[~2016-07-25 8:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-25 8:47 Paul Eggleton [this message]
2016-07-25 8:47 ` [PATCH 1/2] lib/oe/recipeutils: fix patch_recipe*() with empty input Paul Eggleton
2016-07-25 8:47 ` [PATCH 2/2] recipetool: record unknown license files Paul Eggleton
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.1469436396.git.paul.eggleton@linux.intel.com \
--to=paul.eggleton@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.