From: Max Reitz <mreitz@redhat.com>
To: qemu-devel@nongnu.org
Cc: Kevin Wolf <kwolf@redhat.com>, Fam Zheng <famz@redhat.com>,
Markus Armbruster <armbru@redhat.com>,
Stefan Hajnoczi <stefanha@redhat.com>
Subject: Re: [Qemu-devel] [PATCH v4 0/6] iotests: Allow out-of-tree run
Date: Sat, 07 Jun 2014 23:21:13 +0200 [thread overview]
Message-ID: <53938249.4010504@redhat.com> (raw)
In-Reply-To: <1400966700-23165-1-git-send-email-mreitz@redhat.com>
On 24.05.2014 23:24, Max Reitz wrote:
> This series enables qemu-iotests to be run in a build tree outside of
> the source tree. It also makes the tests use the command for invoking
> the Python interpreter specified through configure instead of always
> using "/usr/bin/env python".
Ping; I do understand that this series is not urgent, but since I
realized out-of-tree builds to be probably superior, I personally base
all my own patches on this series, as I don't want to fiddle around with
the iotests. Therefore, I'd be glad if someone would review the
remaining patches so it can be merged soon. :-)
Max
next prev parent reply other threads:[~2014-06-07 21:21 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-24 21:24 [Qemu-devel] [PATCH v4 0/6] iotests: Allow out-of-tree run Max Reitz
2014-05-24 21:24 ` [Qemu-devel] [PATCH v4 1/6] " Max Reitz
2014-05-24 21:24 ` [Qemu-devel] [PATCH v4 2/6] configure: Enable out-of-tree iotests Max Reitz
2014-05-24 21:24 ` [Qemu-devel] [PATCH v4 3/6] iotests: Source common.env Max Reitz
2014-05-24 21:24 ` [Qemu-devel] [PATCH v4 4/6] iotests: Use $PYTHON for Python scripts Max Reitz
2014-05-24 21:24 ` [Qemu-devel] [PATCH v4 5/6] iotests: Drop Python version from 065's Shebang Max Reitz
2014-05-24 21:25 ` [Qemu-devel] [PATCH v4 6/6] iotests: Fix 083 for out-of-tree builds Max Reitz
2014-05-24 21:27 ` [Qemu-devel] [PATCH v4 0/6] iotests: Allow out-of-tree run Max Reitz
2014-06-07 21:21 ` Max Reitz [this message]
2014-06-26 21:42 ` Max Reitz
2014-06-27 11:28 ` Markus Armbruster
2014-06-27 17:58 ` Kevin Wolf
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=53938249.4010504@redhat.com \
--to=mreitz@redhat.com \
--cc=armbru@redhat.com \
--cc=famz@redhat.com \
--cc=kwolf@redhat.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).