From: Fam Zheng <famz@redhat.com>
To: qemu-devel@nongnu.org
Cc: Kevin Wolf <kwolf@redhat.com>,
jcody@redhat.com, jsnow@redhat.com, qemu-block@nongnu.org,
mreitz@redhat.com
Subject: [Qemu-devel] [PATCH 00/10] iotests: Clean up "mv $TEST_IMG $TEST_IMG.XXX"
Date: Wed, 16 Dec 2015 17:54:43 +0800 [thread overview]
Message-ID: <1450259693-25595-1-git-send-email-famz@redhat.com> (raw)
Commit 794d00f71d fixed two "mv" commands into the TEST_IMG override approach.
There are still more occasions of "mv", this series fixes them.
The benefit is it drops the assumption that the created image is a single file,
which is not true for VMDK or the coming QBM format. On top of this, those
formats can be added to these cases later.
The patches stems from QBM work, but I will also take a look at adding
applicable VMDK subformats once merged.
Please review.
Fam
Fam Zheng (10):
iotests: 018: Use TEST_IMG override instead of "mv"
iotests: 019: Use TEST_IMG override instead of "mv"
iotests: 020: Use TEST_IMG override instead of "mv"
iotests: 024: Use TEST_IMG override instead of "mv"
iotests: 028: Use TEST_IMG override instead of "mv"
iotests: 034: Use TEST_IMG override instead of "mv"
iotests: 037: Use TEST_IMG override instead of "mv"
iotests: 038: Use TEST_IMG override instead of "mv"
iotests: 050: Use TEST_IMG override instead of "mv"
iotests: 095: Use TEST_IMG override instead of "mv"
tests/qemu-iotests/018 | 8 ++++----
tests/qemu-iotests/018.out | 2 +-
tests/qemu-iotests/019 | 13 +++++++------
tests/qemu-iotests/019.out | 4 ++--
tests/qemu-iotests/020 | 7 +++++--
tests/qemu-iotests/020.out | 2 +-
tests/qemu-iotests/024 | 10 ++++++++--
tests/qemu-iotests/024.out | 4 ++--
tests/qemu-iotests/028 | 5 ++++-
tests/qemu-iotests/028.out | 2 +-
tests/qemu-iotests/034 | 6 +++++-
tests/qemu-iotests/034.out | 2 +-
tests/qemu-iotests/037 | 5 ++++-
tests/qemu-iotests/037.out | 2 +-
tests/qemu-iotests/038 | 5 ++++-
tests/qemu-iotests/038.out | 2 +-
tests/qemu-iotests/050 | 9 +++++++--
tests/qemu-iotests/050.out | 4 ++--
tests/qemu-iotests/095 | 12 ++++++------
tests/qemu-iotests/095.out | 8 ++++----
20 files changed, 70 insertions(+), 42 deletions(-)
--
2.4.3
next reply other threads:[~2015-12-16 9:55 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-16 9:54 Fam Zheng [this message]
2015-12-16 9:54 ` [Qemu-devel] [PATCH 01/10] iotests: 018: Use TEST_IMG override instead of "mv" Fam Zheng
2015-12-16 9:54 ` [Qemu-devel] [PATCH 02/10] iotests: 019: " Fam Zheng
2015-12-16 9:54 ` [Qemu-devel] [PATCH 03/10] iotests: 020: " Fam Zheng
2015-12-16 9:54 ` [Qemu-devel] [PATCH 04/10] iotests: 024: " Fam Zheng
2015-12-16 9:54 ` [Qemu-devel] [PATCH 05/10] iotests: 028: " Fam Zheng
2015-12-16 9:54 ` [Qemu-devel] [PATCH 06/10] iotests: 034: " Fam Zheng
2015-12-16 9:54 ` [Qemu-devel] [PATCH 07/10] iotests: 037: " Fam Zheng
2015-12-16 9:54 ` [Qemu-devel] [PATCH 08/10] iotests: 038: " Fam Zheng
2015-12-16 9:54 ` [Qemu-devel] [PATCH 09/10] iotests: 050: " Fam Zheng
2015-12-16 9:54 ` [Qemu-devel] [PATCH 10/10] iotests: 095: " Fam Zheng
2015-12-18 18:18 ` Max Reitz
2015-12-22 2:36 ` Fam Zheng
2015-12-18 18:18 ` [Qemu-devel] [PATCH 00/10] iotests: Clean up "mv $TEST_IMG $TEST_IMG.XXX" 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=1450259693-25595-1-git-send-email-famz@redhat.com \
--to=famz@redhat.com \
--cc=jcody@redhat.com \
--cc=jsnow@redhat.com \
--cc=kwolf@redhat.com \
--cc=mreitz@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.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;
as well as URLs for NNTP newsgroup(s).