From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: openembedded-core@lists.openembedded.org
Subject: [PATCH 0/1] Show progress when preparing eSDK (rebased)
Date: Mon, 18 Jul 2016 22:17:02 +1200 [thread overview]
Message-ID: <cover.1468831253.git.paul.eggleton@linux.intel.com> (raw)
This patch from the earlier series wasn't merged, possibly since it
conflicted - I've rebased it onto master and resolved that.
The following changes since commit da7a2c7b00b40a8759dbe9f4ab6df3e337e3d6b6:
useradd-staticids: use map() instead of imap() (2016-07-12 23:11:57 +0100)
are available in the git repository at:
git://git.openembedded.org/openembedded-core-contrib paule/startup-oe2
http://cgit.openembedded.org/cgit.cgi/openembedded-core-contrib/log/?h=paule/startup-oe2
Paul Eggleton (1):
classes/populate_sdk_ext: show progress when preparing build system
meta/classes/populate_sdk_ext.bbclass | 2 +-
meta/files/ext-sdk-prepare.py | 67 ++++++++++++++++++++++-------------
2 files changed, 44 insertions(+), 25 deletions(-)
--
2.5.5
next reply other threads:[~2016-07-18 10:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-18 10:17 Paul Eggleton [this message]
2016-07-18 10:17 ` [PATCH 1/1] classes/populate_sdk_ext: show progress when preparing build system 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.1468831253.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.