From: Eric Blake <eblake@redhat.com>
To: Kevin Wolf <kwolf@redhat.com>
Cc: Mike Day <ncmike@ncultra.org>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
Stefan Hajnoczi <stefanha@redhat.com>
Subject: Re: [Qemu-devel] [PATCH] Add backing file option to qemu-img create help.
Date: Mon, 12 May 2014 11:02:04 -0600 [thread overview]
Message-ID: <5370FE8C.90409@redhat.com> (raw)
In-Reply-To: <20140512163643.GD4371@noname.redhat.com>
[-- Attachment #1: Type: text/plain, Size: 939 bytes --]
On 05/12/2014 10:36 AM, Kevin Wolf wrote:
>>> rebase [-q] [-f fmt] [-t cache] [-p] [-u] -b backing_file [-F
>>> backing_fmt] filename
>>
>> 'rebase' lacks -o; so it must continue to document -b. This thread was
>> started in context to the 'create' subcommand, not the 'rebase'
>> subcommand. (Arguably, we may need to add -o to rebase someday, but
>> that's not for this patch)
>
> What would qemu-img rebase do with -o? It is just for (safely) changing
> the backing file, not for updating options. There is qemu-img amend for
> that, and it does have an -o option.
It's a consistency argument. Why can't we have:
rebase -o backing_file=file,backing_fmt=fmt
similar to create, instead of having to treat rebase as the oddball
command that still takes separate options for two highly related items?
--
Eric Blake eblake redhat com +1-919-301-3266
Libvirt virtualization library http://libvirt.org
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 604 bytes --]
next prev parent reply other threads:[~2014-05-12 17:02 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-12 12:35 [Qemu-devel] [PATCH] Add backing file option to qemu-img create help Mike Day
2014-05-12 15:05 ` Eric Blake
2014-05-12 15:13 ` Kevin Wolf
2014-05-12 15:20 ` Eric Blake
2014-05-12 15:36 ` Mike Day
2014-05-12 15:53 ` Eric Blake
2014-05-12 16:05 ` Mike Day
2014-05-12 16:32 ` Eric Blake
2014-05-12 16:36 ` Kevin Wolf
2014-05-12 17:02 ` Eric Blake [this message]
2014-05-13 8:46 ` Kevin Wolf
2014-05-12 17:10 ` Mike Day
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=5370FE8C.90409@redhat.com \
--to=eblake@redhat.com \
--cc=kwolf@redhat.com \
--cc=ncmike@ncultra.org \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).