From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: openembedded-core@lists.openembedded.org
Subject: [PATCH 0/2] A couple of fixes relating to TEMPLATECONF
Date: Wed, 2 Nov 2016 15:31:03 +1300 [thread overview]
Message-ID: <cover.1478053841.git.paul.eggleton@linux.intel.com> (raw)
The following changes since commit 98c6ebf1e05158c689e01b785d32757847cdb10c:
oeqa/selftest/kernel.py: Add new file destined for kernel related tests (2016-11-01 10:05:40 +0000)
are available in the git repository at:
git://git.openembedded.org/openembedded-core-contrib paule/templateconf
http://cgit.openembedded.org/cgit.cgi/openembedded-core-contrib/log/?h=paule/templateconf
Paul Eggleton (2):
oe-setup-builddir: fix TEMPLATECONF error message
classes/populate_sdk_ext: prevent invalid TEMPLATECONF entering eSDK
meta/classes/populate_sdk_ext.bbclass | 6 +++++-
scripts/oe-setup-builddir | 2 +-
2 files changed, 6 insertions(+), 2 deletions(-)
--
2.5.5
next reply other threads:[~2016-11-02 2:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-02 2:31 Paul Eggleton [this message]
2016-11-02 2:31 ` [PATCH 1/2] oe-setup-builddir: fix TEMPLATECONF error message Paul Eggleton
2016-11-02 2:31 ` [PATCH 2/2] classes/populate_sdk_ext: prevent invalid TEMPLATECONF entering eSDK 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.1478053841.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