All of lore.kernel.org
 help / color / mirror / Atom feed
From: John Snow <jsnow@redhat.com>
To: Eric Blake <eblake@redhat.com>, qemu-block@nongnu.org
Cc: kwolf@redhat.com, qemu-devel@nongnu.org, mreitz@redhat.com
Subject: Re: [Qemu-devel] [PATCH v2] qemu-img: Check for backing image if specified during create
Date: Tue, 9 May 2017 14:21:12 -0400	[thread overview]
Message-ID: <a52155cb-bba7-96ad-9735-a952a3a25d46@redhat.com> (raw)
In-Reply-To: <09281d7d-82f1-fdd8-5f03-669f13b2f09d@redhat.com>



On 05/09/2017 02:19 PM, Eric Blake wrote:
> On 05/09/2017 01:17 PM, Eric Blake wrote:
>> On 05/09/2017 01:09 PM, John Snow wrote:
>>> Or, rather, force the open of a backing image if one was specified
>>> for creation. Using a similar -unsafe option as rebase, allow qemu-img
>>> to ignore the backing file validation if possible.
>>>
> 
>>> +++ b/qemu-img.c
>>> @@ -145,9 +145,11 @@ static void QEMU_NORETURN help(void)
>>>             "  'snapshot_id_or_name' is deprecated, use 'snapshot_param'\n"
>>>             "    instead\n"
>>>             "  '-c' indicates that target image must be compressed (qcow format only)\n"
>>> -           "  '-u' enables unsafe rebasing. It is assumed that old and new backing file\n"
>>> -           "       match exactly. The image doesn't need a working backing file before\n"
>>> -           "       rebasing in this case (useful for renaming the backing file)\n"
>>> +           "  '-u' allows unsafe backing chains. For rebasing, it is assumed that old and new\n"
>>> +           "       backing file match exactly. The image doesn't need a working backing file\n"
>>> +           "       before rebasing in this case (useful for renaming the backing file)\n"
> 
> Also, a '.' to end this sentence would be nice.
> 

d'oh.

I can respin if that's more convenient, as I am assuming Max or Kevin
will have something to say.

If not, either edit it if that's easier, or ask me to re-spin.

>>> +           "       For image creation, allow creating without attempting to"
>>
>> Missing \n
>>
>> With that fixed,
>> Reviewed-by: Eric Blake <eblake@redhat.com>
>>
> 

  reply	other threads:[~2017-05-09 18:21 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-09 18:09 [Qemu-devel] [PATCH v2] qemu-img: Check for backing image if specified during create John Snow
2017-05-09 18:17 ` Eric Blake
2017-05-09 18:19   ` Eric Blake
2017-05-09 18:21     ` John Snow [this message]
2017-05-11  9:37 ` Kevin Wolf
2017-05-11 14:51   ` John Snow

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=a52155cb-bba7-96ad-9735-a952a3a25d46@redhat.com \
    --to=jsnow@redhat.com \
    --cc=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 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.