From: Eric Blake <eblake@redhat.com>
To: qemu-devel@nongnu.org
Cc: kwolf@redhat.com, pkrempa@redhat.com, qemu-block@nongnu.org,
kchamart@redhat.com, libvir-list@redhat.com, mreitz@redhat.com
Subject: Re: [PATCH v5 for-5.0? 0/7] Tighten qemu-img rules on missing backing format
Date: Mon, 4 May 2020 15:02:59 -0500 [thread overview]
Message-ID: <311bb693-4705-b18a-cc92-5865359abaa5@redhat.com> (raw)
In-Reply-To: <20200403175859.863248-1-eblake@redhat.com>
On 4/3/20 12:58 PM, Eric Blake wrote:
> v4 was here:
> https://lists.gnu.org/archive/html/qemu-devel/2020-03/msg03775.html
> In v5:
> - fix 'qemu-img convert -B' to actually warn [Kashyap]
> - squash in followups
> - a couple more iotest improvements
>
> If we decide this is not 5.0 material, then patches 4 and 7 need a
> tweak to s/5.0/5.1/ as the start of the deprecation clock.
Ping. I've already made the 5.1 change in my local tree, does anyone
want to review the rest of this series before I post a v6?
>
> Eric Blake (7):
> sheepdog: Add trivial backing_fmt support
> vmdk: Add trivial backing_fmt support
> qcow: Tolerate backing_fmt=, but warn on backing_fmt=raw
> qcow2: Deprecate use of qemu-img amend to change backing file
> iotests: Specify explicit backing format where sensible
> block: Add support to warn on backing file change without format
> qemu-img: Deprecate use of -b without -F
>
--
Eric Blake, Principal Software Engineer
Red Hat, Inc. +1-919-301-3226
Virtualization: qemu.org | libvirt.org
prev parent reply other threads:[~2020-05-04 20:04 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-03 17:58 [PATCH v5 for-5.0? 0/7] Tighten qemu-img rules on missing backing format Eric Blake
2020-04-03 17:58 ` [PATCH v5 1/7] sheepdog: Add trivial backing_fmt support Eric Blake
2020-04-03 17:58 ` [PATCH v5 2/7] vmdk: " Eric Blake
2020-04-03 17:58 ` [PATCH v5 3/7] qcow: Tolerate backing_fmt=, but warn on backing_fmt=raw Eric Blake
2020-05-05 7:35 ` Kevin Wolf
2020-05-05 15:30 ` Eric Blake
2020-06-22 21:58 ` Eric Blake
2020-06-23 10:40 ` Kevin Wolf
2020-04-03 17:58 ` [PATCH v5 4/7] qcow2: Deprecate use of qemu-img amend to change backing file Eric Blake
2020-05-05 7:50 ` Kevin Wolf
2020-04-03 17:58 ` [PATCH v5 5/7] iotests: Specify explicit backing format where sensible Eric Blake
2020-04-03 17:58 ` [PATCH v5 6/7] block: Add support to warn on backing file change without format Eric Blake
2020-04-03 17:58 ` [PATCH v5 7/7] qemu-img: Deprecate use of -b without -F Eric Blake
2020-05-05 8:11 ` Kevin Wolf
2020-05-05 8:43 ` Peter Krempa
2020-05-04 20:02 ` 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=311bb693-4705-b18a-cc92-5865359abaa5@redhat.com \
--to=eblake@redhat.com \
--cc=kchamart@redhat.com \
--cc=kwolf@redhat.com \
--cc=libvir-list@redhat.com \
--cc=mreitz@redhat.com \
--cc=pkrempa@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 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.