From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: bitbake-devel@lists.openembedded.org
Subject: [1.18][PATCH 0/3] Stable branch cherry-picks
Date: Mon, 20 May 2013 16:20:13 +0100 [thread overview]
Message-ID: <cover.1369063091.git.paul.eggleton@linux.intel.com> (raw)
The following changes (against poky, but apply cleanly with -p2 against
the 1.18 branch of bitbake) are available in the git repository at:
git://git.yoctoproject.org/poky-contrib paule/dylan-next-bb
http://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=paule/dylan-next-bb
Laurentiu Palcu (1):
data_smart.py: add some internal bitbake variables to configuration
hash
Martin Donnelly (1):
goggle: fix invalid error check
Richard Purdie (1):
prserv/cooker: Handle PRService errors cleanly
bitbake/lib/bb/cooker.py | 5 ++++-
bitbake/lib/bb/data_smart.py | 10 ++++++++++
bitbake/lib/bb/ui/goggle.py | 2 +-
bitbake/lib/prserv/serv.py | 9 ++++++---
4 files changed, 21 insertions(+), 5 deletions(-)
--
1.8.1.2
next reply other threads:[~2013-05-20 15:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-20 15:20 Paul Eggleton [this message]
2013-05-20 15:20 ` [1.18][PATCH 1/3] goggle: fix invalid error check Paul Eggleton
2013-05-20 15:20 ` [1.18][PATCH 2/3] prserv/cooker: Handle PRService errors cleanly Paul Eggleton
2013-05-20 15:20 ` [1.18][PATCH 3/3] data_smart.py: add some internal bitbake variables to configuration hash 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.1369063091.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