From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: bitbake-devel@lists.openembedded.org
Subject: [PATCH 0/2] Error handling fixes
Date: Thu, 29 May 2014 18:17:14 +0100 [thread overview]
Message-ID: <cover.1401383609.git.paul.eggleton@linux.intel.com> (raw)
The following changes since commit 0e7b594ccbceb3149f38776cea204807031ef69f:
fetch2/hg: Fix missing proto param for hg checkout with user and pw (2014-05-28 08:28:17 +0100)
are available in the git repository at:
git://git.yoctoproject.org/poky-contrib paule/bb-errors
http://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=paule/bb-errors
Paul Eggleton (2):
fetch2: improve handling of two classes of URL parameter mistakes
utils: avoid printing traceback on ExpansionError during parsing
lib/bb/fetch2/__init__.py | 14 ++++++++++----
lib/bb/utils.py | 2 ++
2 files changed, 12 insertions(+), 4 deletions(-)
--
1.9.3
next reply other threads:[~2014-05-29 17:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-29 17:17 Paul Eggleton [this message]
2014-05-29 17:17 ` [PATCH 1/2] fetch2: improve handling of two classes of URL parameter mistakes Paul Eggleton
2014-05-29 17:17 ` [PATCH 2/2] utils: avoid printing traceback on ExpansionError during parsing 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.1401383609.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