From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: openembedded-core@lists.openembedded.org
Subject: [PATCH 0/2] Path-related fixes for the extensible SDK
Date: Wed, 14 Sep 2016 17:09:50 +1200 [thread overview]
Message-ID: <cover.1473829704.git.paul.eggleton@linux.intel.com> (raw)
The following changes since commit 4d268abc2fc892c5d34449f78c8e9f2b1a9d6bac:
oeqa.runtime.smart: work around smart race issues (2016-09-09 12:12:17 +0100)
are available in the git repository at:
git://git.openembedded.org/openembedded-core-contrib paule/extsdk-path-fixes
http://cgit.openembedded.org/cgit.cgi/openembedded-core-contrib/log/?h=paule/extsdk-path-fixes
Paul Eggleton (2):
classes/populate_sdk_ext: ensure we clean the right temporary TMPDIR path
lib/oe/copy_buildsystem: fix building eSDK with indirect paths in BBLAYERS
meta/classes/populate_sdk_ext.bbclass | 7 ++++---
meta/lib/oe/copy_buildsystem.py | 4 ++--
2 files changed, 6 insertions(+), 5 deletions(-)
--
2.5.5
next reply other threads:[~2016-09-14 5:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-14 5:09 Paul Eggleton [this message]
2016-09-14 5:09 ` [PATCH 1/2] classes/populate_sdk_ext: ensure we clean the right temporary TMPDIR path Paul Eggleton
2016-09-14 5:09 ` [PATCH 2/2] lib/oe/copy_buildsystem: fix building eSDK with indirect paths in BBLAYERS 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.1473829704.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