From: <kai.kang@windriver.com>
To: <openembedded-core@lists.openembedded.org>
Subject: [PATCH 0/1] Fix screen parallel build failure
Date: Thu, 27 Aug 2015 17:28:58 +0800 [thread overview]
Message-ID: <cover.1440667679.git.kai.kang@windriver.com> (raw)
From: Kai Kang <kai.kang@windriver.com>
The following changes since commit 393bd7496d71eb101f21234c1233a2d18fd2c73e:
oeqa/oetest.py: add better package search for hasPackage() (2015-08-26 08:28:06 +0100)
are available in the git repository at:
git://git.yoctoproject.org/poky-contrib kangkai/screen
http://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=kangkai/screen
Kai Kang (1):
screen: fix parallel build failure
.../screen/0001-fix-for-multijob-build.patch | 58 ++++++++++++++++++++++
meta/recipes-extended/screen/screen_4.3.1.bb | 4 +-
2 files changed, 61 insertions(+), 1 deletion(-)
create mode 100644 meta/recipes-extended/screen/screen/0001-fix-for-multijob-build.patch
--
1.9.1
next reply other threads:[~2015-08-27 9:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-27 9:28 kai.kang [this message]
2015-08-27 9:28 ` [PATCH 1/1] screen: fix parallel build failure kai.kang
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.1440667679.git.kai.kang@windriver.com \
--to=kai.kang@windriver.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