All of lore.kernel.org
 help / color / mirror / Atom feed
From: Max Reitz <mreitz@redhat.com>
To: Eric Blake <eblake@redhat.com>, qemu-block@nongnu.org
Cc: qemu-devel@nongnu.org, Kevin Wolf <kwolf@redhat.com>,
	qemu-stable <qemu-stable@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH for-2.10 3/3] qemu-img/convert: Move bs_n > 1 && -B check down
Date: Wed, 19 Apr 2017 14:38:36 +0200	[thread overview]
Message-ID: <23949686-9e74-6eb7-6f8c-c129f83d8faf@redhat.com> (raw)
In-Reply-To: <25e5ee1f-3bc7-d657-59db-c4e59baf8e28@redhat.com>

[-- Attachment #1: Type: text/plain, Size: 1615 bytes --]

On 13.04.2017 23:17, Eric Blake wrote:
> On 04/13/2017 03:34 PM, Max Reitz wrote:
>> It does not make much sense to use a backing image for the target when
>> you concatenate multiple images (because then there is no correspondence
>> between the source images' backing files and the target's); but it was
>> still possible to give one by using -o backing_file=X instead of -B X.
>>
>> Fix this by moving the check.
>>
>> (Also, change the error message because -B is not the only way to
>>  specify the backing file, evidently.)
> 
> For that matter, 'create -B' is intentionally? undocumented in the
> qemu-img --help and man page.  (Personally, I don't know why we don't
> want it documented - is it because it it not a universal option because
> not all formats support backing files?)

(I suppose you mean convert instead of create)

Well, the man page at least documents that you can use backing_file for
the destination and what it will do. So documenting would probably be
just "Oh, you can also use -B, by the way."

I won't promise to write a patch to fix that, but I do hope I will. :-)

>> Cc: qemu-stable <qemu-stable@nongnu.org>
>> Signed-off-by: Max Reitz <mreitz@redhat.com>
>> ---
>>  qemu-img.c                 | 14 +++++++-------
>>  tests/qemu-iotests/122.out |  4 ++--
>>  2 files changed, 9 insertions(+), 9 deletions(-)
>>
> 
> Reviewed-by: Eric Blake <eblake@redhat.com>

Thanks, as always!

Max

> Having a backing file for the destination may still make sense for some
> convoluted workflow, but you can get that with a followup qemu-img rebase.


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

  reply	other threads:[~2017-04-19 12:38 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-13 20:33 [Qemu-devel] [PATCH for-2.10 0/3] qemu-img/convert: Some small fixes Max Reitz
2017-04-13 20:33 ` [Qemu-devel] [PATCH for-2.10 1/3] qemu-img/convert: Always set ret < 0 on error Max Reitz
2017-04-13 21:10   ` Eric Blake
2017-04-14 15:27   ` Philippe Mathieu-Daudé
2017-04-13 20:34 ` [Qemu-devel] [PATCH for-2.10 2/3] qemu-img/convert: Use @opts for one thing only Max Reitz
2017-04-13 21:13   ` Eric Blake
2017-04-13 20:34 ` [Qemu-devel] [PATCH for-2.10 3/3] qemu-img/convert: Move bs_n > 1 && -B check down Max Reitz
2017-04-13 21:17   ` Eric Blake
2017-04-19 12:38     ` Max Reitz [this message]
2017-04-19 15:49 ` [Qemu-devel] [PATCH for-2.10 0/3] qemu-img/convert: Some small fixes Kevin Wolf
2017-04-26 12:48   ` Max Reitz
2017-04-26 13:06     ` 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=23949686-9e74-6eb7-6f8c-c129f83d8faf@redhat.com \
    --to=mreitz@redhat.com \
    --cc=eblake@redhat.com \
    --cc=kwolf@redhat.com \
    --cc=qemu-block@nongnu.org \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-stable@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.