From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: "Patches and discussions about the oe-core layer"
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 0/2] Fix TMPDIR usage in scripts
Date: Wed, 28 Sep 2011 12:25:41 +0100 [thread overview]
Message-ID: <201109281225.41524.paul.eggleton@linux.intel.com> (raw)
In-Reply-To: <1317208204.26109.240.camel@ted>
On Wednesday 28 September 2011 12:09:57 Richard Purdie wrote:
> At the very least we need to fix the references in
> scripts/qemuimage-testlib so the automated image testing doesn't break.
OK, v2 on its way. The scripts that call qemuimage-testlib will still need to
be updated to set OE_TMPDIR though.
Cheers,
Paul
--
Paul Eggleton
Intel Open Source Technology Centre
next prev parent reply other threads:[~2011-09-28 11:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-28 9:26 [PATCH 0/2] Fix TMPDIR usage in scripts Paul Eggleton
2011-09-28 9:26 ` [PATCH 1/2] scripts: use OE_TMPDIR instead of TMPDIR external variable Paul Eggleton
2011-09-28 9:26 ` [PATCH 2/2] scripts/oe-setup-rpmrepo: use setup_tmpdir from runqemu Paul Eggleton
2011-09-28 11:09 ` [PATCH 0/2] Fix TMPDIR usage in scripts Richard Purdie
2011-09-28 11:25 ` Paul Eggleton [this message]
2011-09-28 11:38 ` Richard Purdie
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=201109281225.41524.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