Re: [PATCH for-5.0? v4 0/7] Tighten qemu-img rules on missing backing format

[Eric Blake <eblake@redhat.com>]

On 3/12/20 2:28 PM, Eric Blake wrote:
> v3 was here:
> https://lists.gnu.org/archive/html/qemu-devel/2020-03/msg01730.html
> In v4:
> - old patch 1 was reworked into new patch 1-3, with stricter rules
> on which backing formats are accepted [Kevin]
> - patch 4 is new: amend is handled differently from rebase [Kashyap]
> - rebase to master
> 
> 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

Is this still worth trying to get in 5.0?  There were not many comments 
on v4, other than a compile fix I need to squash in and Kashyap asking a 
question on qemu-img convert behavior that I still need to double-check, 
or at a bare minimum add iotest coverage for.  But depending on the 
urgency to get this in now, vs. delaying the deprecation clock for 4 
more months by starting it in 5.1, determines how much effort I need to 
put in getting a v5 out right now.

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