From: Eric Blake <eblake@redhat.com>
To: Fam Zheng <famz@redhat.com>, Max Reitz <mreitz@redhat.com>
Cc: Kevin Wolf <kwolf@redhat.com>,
Peter Maydell <peter.maydell@linaro.org>,
qemu-devel@nongnu.org, Stefan Hajnoczi <stefanha@redhat.com>,
Markus Armbruster <armbru@redhat.com>
Subject: Re: [Qemu-devel] [PATCH v3 3/7] iotests: Add default common.env
Date: Fri, 23 May 2014 06:27:29 -0600 [thread overview]
Message-ID: <537F3EB1.3030200@redhat.com> (raw)
In-Reply-To: <20140523061001.GG1668@T430.nay.redhat.com>
[-- Attachment #1: Type: text/plain, Size: 840 bytes --]
On 05/23/2014 12:10 AM, Fam Zheng wrote:
> On Thu, 05/22 23:30, Max Reitz wrote:
>> Add a default common.env in case the one supposed to be emitted by
>> configure cannot be found.
>>
>> Signed-off-by: Max Reitz <mreitz@redhat.com>
>
> Now we can run both from in-tree build and out-of-tree build without this,
> which is already very good, but we need this patch to run from the source tree
> with an out-of-tree build. I'm not sure we really need that, though.
If you have a source tree but no in-tree build, then there is no way to
know how many out-of-tree builds there are, or which one you should
pick. If you are going to do out-of-tree builds, you aren't going to
try to run tests from the source tree.
--
Eric Blake eblake redhat com +1-919-301-3266
Libvirt virtualization library http://libvirt.org
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 604 bytes --]
next prev parent reply other threads:[~2014-05-23 12:27 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-22 21:30 [Qemu-devel] [PATCH v3 0/7] iotests: Allow out-of-tree run Max Reitz
2014-05-22 21:30 ` [Qemu-devel] [PATCH v3 1/7] " Max Reitz
2014-05-23 3:44 ` Fam Zheng
2014-05-22 21:30 ` [Qemu-devel] [PATCH v3 2/7] configure: Enable out-of-tree iotests Max Reitz
2014-05-23 3:47 ` Fam Zheng
2014-05-24 19:27 ` Max Reitz
2014-05-22 21:30 ` [Qemu-devel] [PATCH v3 3/7] iotests: Add default common.env Max Reitz
2014-05-23 6:10 ` Fam Zheng
2014-05-23 12:27 ` Eric Blake [this message]
2014-05-23 13:33 ` Markus Armbruster
2014-05-24 19:40 ` Max Reitz
2014-05-22 21:30 ` [Qemu-devel] [PATCH v3 4/7] iotests: Source common.env Max Reitz
2014-05-23 4:01 ` Fam Zheng
2014-05-24 20:18 ` Max Reitz
2014-05-22 21:30 ` [Qemu-devel] [PATCH v3 5/7] iotests: Use $PYTHON for Python scripts Max Reitz
2014-05-23 3:58 ` Fam Zheng
2014-05-24 19:35 ` Max Reitz
2014-05-22 21:30 ` [Qemu-devel] [PATCH v3 6/7] iotests: Drop Python version from 065's Shebang Max Reitz
2014-05-23 4:02 ` Fam Zheng
2014-05-22 21:30 ` [Qemu-devel] [PATCH v3 7/7] iotests: Fix 083 for out-of-tree builds Max Reitz
2014-05-22 21:35 ` [Qemu-devel] [PATCH v3 0/7] iotests: Allow out-of-tree run Max Reitz
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=537F3EB1.3030200@redhat.com \
--to=eblake@redhat.com \
--cc=armbru@redhat.com \
--cc=famz@redhat.com \
--cc=kwolf@redhat.com \
--cc=mreitz@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.com \
/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.