From: "Ján Tomko" <jtomko@redhat.com>
To: Eric Blake <eblake@redhat.com>
Cc: Kevin Wolf <kwolf@redhat.com>,
pkrempa@redhat.com, qemu-block@nongnu.org,
libvir-list@redhat.com, qemu-devel@nongnu.org, mreitz@redhat.com,
John Snow <jsnow@redhat.com>
Subject: Re: [PATCH v2 2/3] block: Add support to warn on backing file change without format
Date: Thu, 27 Feb 2020 10:22:22 +0100 [thread overview]
Message-ID: <20200227092222.GE2262365@lpt> (raw)
In-Reply-To: <20200227023928.1021959-3-eblake@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 604 bytes --]
On a Wednesday in 2020, Eric Blake wrote:
>For now, this is a mechanical addition; all callers pass false. But
>the next patch will use it to improve 'qemu-img rebase -u' when
>selecting a backing file with no format.
>
>Signed-off-by: Eric Blake <eblake@redhat.com>
>---
> include/block/block.h | 4 ++--
> block.c | 13 ++++++++++---
> block/qcow2.c | 2 +-
> block/stream.c | 2 +-
> blockdev.c | 3 ++-
> qemu-img.c | 4 ++--
> 6 files changed, 18 insertions(+), 10 deletions(-)
>
Reviewed-by: Ján Tomko <jtomko@redhat.com>
Jano
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2020-02-27 9:23 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-27 2:39 [PATCH v2 0/3] Tighten qemu-img rules on missing backing format Eric Blake
2020-02-27 2:39 ` [PATCH v2 1/3] iotests: Specify explicit backing format where sensible Eric Blake
2020-02-27 7:20 ` Peter Krempa
2020-02-27 9:03 ` Ján Tomko
2020-02-27 13:05 ` Eric Blake
2020-02-27 9:19 ` Ján Tomko
2020-02-27 13:08 ` Eric Blake
2020-03-05 22:58 ` Eric Blake
2020-02-27 2:39 ` [PATCH v2 2/3] block: Add support to warn on backing file change without format Eric Blake
2020-02-27 7:10 ` Peter Krempa
2020-02-27 9:22 ` Ján Tomko [this message]
2020-02-27 2:39 ` [PATCH v2 3/3] qemu-img: Deprecate use of -b without -F Eric Blake
2020-02-27 7:09 ` Peter Krempa
2020-02-27 13:13 ` Eric Blake
2020-02-27 9:43 ` Ján Tomko
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=20200227092222.GE2262365@lpt \
--to=jtomko@redhat.com \
--cc=eblake@redhat.com \
--cc=jsnow@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.