From: Robert Yang <liezhi.yang@windriver.com>
To: <openembedded-core@lists.openembedded.org>
Subject: [PATCH 0/2 V2] fixes for prserver
Date: Wed, 11 Nov 2015 23:34:38 -0800 [thread overview]
Message-ID: <cover.1447313581.git.liezhi.yang@windriver.com> (raw)
* V2:
- Let bitbake-prserv-tool check filename for both .inc and .conf
// Robert
The following changes since commit e44ed8c18e395b9c055aefee113b90708e8a8a2f:
build-appliance-image: Update to jethro head revision (2015-11-03 14:02:57 +0000)
are available in the git repository at:
git://git.openembedded.org/openembedded-core-contrib oe_contrib/rbt/prserv
http://cgit.openembedded.org/cgit.cgi/openembedded-core-contrib/log/?h=rbt/prserv
Robert Yang (2):
prexport.bbclass: avoid export for native and crosssdk
bitbake-prserv-tool: check file name
meta/classes/prexport.bbclass | 5 +++--
scripts/bitbake-prserv-tool | 9 +++++++++
2 files changed, 12 insertions(+), 2 deletions(-)
--
1.7.9.5
next reply other threads:[~2015-11-12 7:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-12 7:34 Robert Yang [this message]
2015-11-12 7:34 ` [PATCH 1/2] prexport.bbclass: avoid export for native and crosssdk Robert Yang
2015-11-12 7:34 ` [PATCH 2/2] bitbake-prserv-tool: check file name Robert Yang
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.1447313581.git.liezhi.yang@windriver.com \
--to=liezhi.yang@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