From: Markus Armbruster <armbru@redhat.com>
To: qemu-devel@nongnu.org
Cc: kwolf@redhat.com, stefanha@redhat.com, qemu-block@nongnu.org,
mreitz@redhat.com
Subject: [Qemu-devel] [PATCH 0/2] Unbreak qemu-img error messages and iotests
Date: Sat, 14 Mar 2015 10:23:13 +0100 [thread overview]
Message-ID: <1426324995-28192-1-git-send-email-armbru@redhat.com> (raw)
"check -T -qcow2" now passes again. Sorry for the mess I made.
Markus Armbruster (2):
iotests: Update 051's reference output
qemu-img: Fix convert, amend error messages for unknown options
qemu-img.c | 6 ++----
tests/qemu-iotests/051.out | 4 +---
tests/qemu-iotests/061.out | 1 -
3 files changed, 3 insertions(+), 8 deletions(-)
--
1.9.3
next reply other threads:[~2015-03-14 9:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-14 9:23 Markus Armbruster [this message]
2015-03-14 9:23 ` [Qemu-devel] [PATCH 1/2] iotests: Update 051's reference output Markus Armbruster
2015-03-14 9:23 ` [Qemu-devel] [PATCH 2/2] qemu-img: Fix convert, amend error messages for unknown options Markus Armbruster
2015-03-16 12:00 ` [Qemu-devel] [PATCH 0/2] Unbreak qemu-img error messages and iotests 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=1426324995-28192-1-git-send-email-armbru@redhat.com \
--to=armbru@redhat.com \
--cc=kwolf@redhat.com \
--cc=mreitz@redhat.com \
--cc=qemu-block@nongnu.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 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).