From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: openembedded-core@lists.openembedded.org
Subject: [PATCH 0/2] recipetool npm regression fixes
Date: Thu, 24 Aug 2017 00:14:46 +1200 [thread overview]
Message-ID: <cover.1503490439.git.paul.eggleton@linux.intel.com> (raw)
Fixes for a couple of regressions caused by recent patches to
recipetool.
The following changes since commit f59e729f98ef9b506b0cfdc415567e03ec87f2a9:
runqemu: Use virtio to mount cdrom drives (2017-08-23 12:06:46 +0100)
are available in the git repository at:
git://git.openembedded.org/openembedded-core-contrib paule/recipetool-npm-fixes2
http://cgit.openembedded.org/openembedded-core-contrib/log/?h=paule/recipetool-npm-fixes2
Paul Eggleton (2):
recipetool: create: fix broken import in npm module
recipetool: create: fix npm license code regression
scripts/lib/recipetool/create_npm.py | 5 ++++-
1 file changed, 4 insertions(+), 1 deletion(-)
--
2.9.5
next reply other threads:[~2017-08-23 12:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-23 12:14 Paul Eggleton [this message]
2017-08-23 12:14 ` [PATCH 1/2] recipetool: create: fix broken import in npm module Paul Eggleton
2017-08-23 12:14 ` [PATCH 2/2] recipetool: create: fix npm license code regression 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.1503490439.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.