From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: openembedded-core@lists.openembedded.org
Subject: [PATCH 0/1] devtool: package: don't try to initialise tinfoil twice
Date: Wed, 14 Dec 2016 21:49:49 +1300 [thread overview]
Message-ID: <cover.1481705295.git.paul.eggleton@linux.intel.com> (raw)
This patch is on top of the tinfoil2 set but doesn't actually require it -
it fixes an issue that's been there for a while, it just slowed things
down a bit instead of failing as it does with tinfoil2.
The following changes since commit 2eea6a65b009e9d47c03b7d82d2699f88228fc62:
oe-selftest: add basic tinfoil tests (2016-12-13 19:55:02 +1300)
are available in the git repository at:
git://git.openembedded.org/openembedded-core-contrib paule/tinfoil2-extra-fix
http://cgit.openembedded.org/cgit.cgi/openembedded-core-contrib/log/?h=paule/tinfoil2-extra-fix
Paul Eggleton (1):
devtool: package: don't try to initialise tinfoil twice
scripts/lib/devtool/package.py | 4 +---
1 file changed, 1 insertion(+), 3 deletions(-)
--
2.5.5
next reply other threads:[~2016-12-14 8:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-14 8:49 Paul Eggleton [this message]
2016-12-14 8:49 ` [PATCH 1/1] devtool: package: don't try to initialise tinfoil twice 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.1481705295.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