From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: bitbake-devel@lists.openembedded.org
Subject: [PATCH 0/3] npm fetcher fixes
Date: Mon, 7 Mar 2016 17:27:34 +1300 [thread overview]
Message-ID: <cover.1457324829.git.paul.eggleton@linux.intel.com> (raw)
The following changes since commit 19507b80f35d37dc4b1614bd390b8e261dd4a2bd:
bitbake-user-manual: Added expand() function to list. (2016-03-03 17:33:59 +0000)
are available in the git repository at:
git://git.yoctoproject.org/poky-contrib paule/bb-npm-fixes
http://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=paule/bb-npm-fixes
Paul Eggleton (3):
fetch2/npm: fix indentation
fetch2/npm: handle alternative dependency syntax
fetch2/npm: ignore unknown headers in tarballs
lib/bb/fetch2/npm.py | 50 ++++++++++++++++++++++++++------------------------
1 file changed, 26 insertions(+), 24 deletions(-)
--
2.5.0
next reply other threads:[~2016-03-07 4:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-07 4:27 Paul Eggleton [this message]
2016-03-07 4:27 ` [PATCH 1/3] fetch2/npm: fix indentation Paul Eggleton
2016-03-07 4:27 ` [PATCH 2/3] fetch2/npm: handle alternative dependency syntax Paul Eggleton
2016-03-07 4:27 ` [PATCH 3/3] fetch2/npm: ignore unknown headers in tarballs 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.1457324829.git.paul.eggleton@linux.intel.com \
--to=paul.eggleton@linux.intel.com \
--cc=bitbake-devel@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