From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: openembedded-core@lists.openembedded.org
Subject: [PATCH 0/4] Extensible SDK fixes
Date: Wed, 13 Jan 2016 07:47:43 +1300 [thread overview]
Message-ID: <cover.1452624350.git.paul.eggleton@linux.intel.com> (raw)
The following changes since commit 541315d6c56df6448f64c262f99d43d5c1e9400b:
update_font_cache: only scan system font directories (2016-01-11 23:23:18 +0000)
are available in the git repository at:
git://git.openembedded.org/openembedded-core-contrib paule/extsdkfixes4-oe
http://cgit.openembedded.org/cgit.cgi/openembedded-core-contrib/log/?h=paule/extsdkfixes4-oe
Paul Eggleton (4):
classes/populate_sdk_ext.bbclass: handle if local.conf doesn't end with a newline
classes/populate_sdk_ext: support auto.conf
classes/buildhistory: save auto.conf and bblayers.conf for extensible SDK
classes/populate_sdk_ext: check that extensible SDK prepared correctly
meta/classes/buildhistory.bbclass | 2 +-
meta/classes/populate_sdk_ext.bbclass | 20 ++++++--
meta/files/ext-sdk-prepare.py | 92 +++++++++++++++++++++++++++++++++++
meta/files/ext-sdk-prepare.sh | 8 ---
4 files changed, 110 insertions(+), 12 deletions(-)
create mode 100644 meta/files/ext-sdk-prepare.py
delete mode 100644 meta/files/ext-sdk-prepare.sh
--
2.5.0
next reply other threads:[~2016-01-12 18:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-12 18:47 Paul Eggleton [this message]
2016-01-12 18:47 ` [PATCH 1/4] classes/populate_sdk_ext.bbclass: handle if local.conf doesn't end with a newline Paul Eggleton
2016-01-12 18:47 ` [PATCH 2/4] classes/populate_sdk_ext: support auto.conf Paul Eggleton
2016-01-12 18:47 ` [PATCH 3/4] classes/buildhistory: save auto.conf and bblayers.conf for extensible SDK Paul Eggleton
2016-01-12 18:47 ` [PATCH 4/4] classes/populate_sdk_ext: check that extensible SDK prepared correctly Paul Eggleton
-- strict thread matches above, loose matches on Subject: below --
2015-10-13 16:53 [PATCH 0/4] Extensible SDK fixes 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.1452624350.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