qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Eric Blake <eblake@redhat.com>
To: Kevin Wolf <kwolf@redhat.com>
Cc: qemu-devel@nongnu.org, "open list:qcow2" <qemu-block@nongnu.org>,
	Max Reitz <mreitz@redhat.com>
Subject: Re: [Qemu-devel] [PATCH for-4.1] qcow2: Allow -o compat=v3 during qemu-img amend
Date: Mon, 8 Jul 2019 14:15:10 -0500	[thread overview]
Message-ID: <dd2d4013-799a-3ddf-c7a9-48d72aaa756d@redhat.com> (raw)
In-Reply-To: <20190708165112.GA14296@linux.fritz.box>


[-- Attachment #1.1: Type: text/plain, Size: 1130 bytes --]

On 7/8/19 11:51 AM, Kevin Wolf wrote:
> Am 05.07.2019 um 17:28 hat Eric Blake geschrieben:
>> Commit b76b4f60 allowed '-o compat=v3' as an alias for the
>> less-appealing '-o compat=1.1' for 'qemu-img create' since we want to
>> use the QMP form as much as possible, but forgot to do likewise for
>> qemu-img amend.  Also, it doesn't help that '-o help' doesn't list our
>> new preferred spellings.
>>
>> Signed-off-by: Eric Blake <eblake@redhat.com>
> 
> This broke qemu-iotests 082. Please send a follow-up to update the
> reference output.

I know that I did not specifically run iotests explicitly for this one
patch, but thought I had at least ran 'make check', since I know we've
been improving lately to run at least some of the iotests.

/me goes and rechecks...

well, 82 is definitely marked 'auto', and group claims that auto tests
will be run by 'make check', but that didn't trigger the failure for me.
 I wonder why?  At least I've posted the fix, as requested.

-- 
Eric Blake, Principal Software Engineer
Red Hat, Inc.           +1-919-301-3226
Virtualization:  qemu.org | libvirt.org


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

      reply	other threads:[~2019-07-08 19:18 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-05 15:28 [Qemu-devel] [PATCH for-4.1] qcow2: Allow -o compat=v3 during qemu-img amend Eric Blake
2019-07-05 15:53 ` Eric Blake
2019-07-05 15:55   ` Eric Blake
2019-07-08 14:04 ` Kevin Wolf
2019-07-08 16:51 ` Kevin Wolf
2019-07-08 19:15   ` Eric Blake [this message]

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=dd2d4013-799a-3ddf-c7a9-48d72aaa756d@redhat.com \
    --to=eblake@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).