From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: openembedded-core@lists.openembedded.org
Subject: [PATCH 0/2] Locked sstate / SDK changes
Date: Wed, 10 Sep 2014 18:19:30 +0100 [thread overview]
Message-ID: <cover.1410369386.git.paul.eggleton@linux.intel.com> (raw)
A couple of changes related to the developer workflow work (see
https://bugzilla.yoctoproject.org/show_bug.cgi?id=6662 ).
Unfortunately the user facing parts of that are some way off
being ready for submission but here are a couple of the minimal
core pieces we need to make those work.
(Note that these are on top of Richard's locked sigs changes that
are still in review.)
The following changes since commit 00e869965818a08cec1ec4f48c35dcf0fe0d6959:
sstatesig: Improve to handle locking of multiple machines (2014-09-10 18:15:41 +0100)
are available in the git repository at:
git://git.openembedded.org/openembedded-core-contrib paule/sdkchanges
http://cgit.openembedded.org/cgit.cgi/openembedded-core-contrib/log/?h=paule/sdkchanges
Paul Eggleton (1):
classes/populate_sdk_base: enable adding custom commands to SDK
install script
Randy Witt (1):
sstatesig.py: Add a path argument to dump_lockedsigs()
meta/classes/populate_sdk_base.bbclass | 7 +++++++
meta/files/toolchain-shar-template.sh | 2 ++
meta/lib/oe/sstatesig.py | 7 ++++---
3 files changed, 13 insertions(+), 3 deletions(-)
--
1.9.3
next reply other threads:[~2014-09-10 17:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-10 17:19 Paul Eggleton [this message]
2014-09-10 17:19 ` [PATCH 1/2] classes/populate_sdk_base: enable adding custom commands to SDK install script Paul Eggleton
2014-09-10 17:19 ` [PATCH 2/2] sstatesig.py: Add a path argument to dump_lockedsigs() Paul Eggleton
2014-09-11 16:39 ` [PATCH 0/2] Locked sstate / SDK changes Burton, Ross
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.1410369386.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