From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: openembedded-core@lists.openembedded.org
Subject: [PATCH 0/3] devtool add fixes
Date: Tue, 4 Oct 2016 22:31:13 +1300 [thread overview]
Message-ID: <cover.1475573453.git.paul.eggleton@linux.intel.com> (raw)
The following changes since commit 21cc2a3f63ea260dbf6b50e2fd4dd50cacdd9935:
machine-sdk: Clear ABIEXTENSION to avoid sstate checksum mismatch issues (2016-10-01 08:16:03 +0100)
are available in the git repository at:
git://git.openembedded.org/openembedded-core-contrib paule/devtool21-oe
http://cgit.openembedded.org/cgit.cgi/openembedded-core-contrib/log/?h=paule/devtool21-oe
Paul Eggleton (3):
devtool: add: fix error message when only specifying a recipe name
devtool: add: display a warning for deprecated -f/--fetch option
devtool: add: build nodejs-native if npm is needed and not available
scripts/lib/devtool/__init__.py | 29 +++++++++++++++++++++++++++++
scripts/lib/devtool/standard.py | 35 ++++++++++++++++++++++++-----------
scripts/lib/recipetool/create.py | 10 ++++++----
scripts/lib/recipetool/create_npm.py | 4 +++-
4 files changed, 62 insertions(+), 16 deletions(-)
--
2.5.5
next reply other threads:[~2016-10-04 9:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-04 9:31 Paul Eggleton [this message]
2016-10-04 9:31 ` [PATCH 1/3] devtool: add: fix error message when only specifying a recipe name Paul Eggleton
2016-10-04 9:31 ` [PATCH 2/3] devtool: add: display a warning for deprecated -f/--fetch option Paul Eggleton
2016-10-04 9:31 ` [PATCH 3/3] devtool: add: build nodejs-native if npm is needed and not available 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.1475573453.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox