All of lore.kernel.org
 help / color / mirror / Atom feed
From: Wenchao Xia <xiawenc@linux.vnet.ibm.com>
To: Eric Blake <eblake@redhat.com>, qemu-devel@nongnu.org
Cc: kwolf@redhat.com, pbonzini@redhat.com, jcody@redhat.com,
	stefanha@redhat.com
Subject: Re: [Qemu-devel] [PATCH V7 4/6] qemu-img: add -l for snapshot in convert
Date: Mon, 16 Dec 2013 10:47:58 +0800	[thread overview]
Message-ID: <52AE69DE.1000702@linux.vnet.ibm.com> (raw)
In-Reply-To: <52AB0F2C.5030703@redhat.com>

于 2013/12/13 21:44, Eric Blake 写道:
> On 12/08/2013 08:43 PM, Wenchao Xia wrote:
>>>>
>>>> convert -s snapshot.name=name1
>>>>
>>>     Previous I planned to use -l for internal snapshot in all possible
>>> program, since -s is taken as external snapshot in qemu, qemu-nbd.
>
> Consistency in command line options between different tools is nice, but
> is less important than adding functionality.  I'm perfectly fine if we
> use -l in one tool and -s in another, as long as the documentation is
> clear on how to spell the option for the tool I want to use.
>
>>> let -s stands for internal in qemu-img convert only, may bring
>>> confuse to user, so I deprecated it instead of enhance it(I want
>>> to remove it but may bring compatiablity issue).
>>>     Yes, it should report error when both specified, will send a patch
>>> if you agree '-l' should still be used.
>>>
>>>
>>    Eric, I hope to get your idea before patching, any comments?
>>
>
> My biggest concern was that by adding -l as a superset of -s, but not
> taking care of the relation between the two, you created odd command
> line usage patterns.  For qemu-img, it may be simpler to just make -s do
> everything, instead of trying to deprecate it (that is, adding -l for
> consistency with other tools while breaking -s isn't nice).
>
   OK, there is still one cornor case to consider:
-s snapshot.name=name1
   It may change the semantics if a caller used qemu-img convert as
above before, although it seems insane.:)

  reply	other threads:[~2013-12-16  2:48 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-04  9:10 [Qemu-devel] [PATCH V7 0/6] export internal snapshot by qemu-nbd Wenchao Xia
2013-12-04  9:10 ` [Qemu-devel] [PATCH V7 1/6] snapshot: distinguish id and name in load_tmp Wenchao Xia
2013-12-04  9:10 ` [Qemu-devel] [PATCH V7 2/6] qemu-nbd: support internal snapshot export Wenchao Xia
2013-12-04  9:10 ` [Qemu-devel] [PATCH V7 3/6] qemu-iotests: add 058 internal snapshot export with qemu-nbd case Wenchao Xia
2014-01-16 12:52   ` Kevin Wolf
2014-01-17  3:00     ` Wenchao Xia
2013-12-04  9:10 ` [Qemu-devel] [PATCH V7 4/6] qemu-img: add -l for snapshot in convert Wenchao Xia
2013-12-04 20:42   ` Eric Blake
2013-12-05  6:06     ` Wenchao Xia
2013-12-09  3:43       ` Wenchao Xia
2013-12-13 13:44         ` Eric Blake
2013-12-16  2:47           ` Wenchao Xia [this message]
2013-12-04  9:10 ` [Qemu-devel] [PATCH V7 5/6] qemu-iotests: add test for snapshot in qemu-img convert Wenchao Xia
2013-12-04  9:10 ` [Qemu-devel] [PATCH V7 6/6] qemu-nbd: add doc for option -f Wenchao Xia
2013-12-04 14:52 ` [Qemu-devel] [PATCH V7 0/6] export internal snapshot by qemu-nbd Stefan Hajnoczi

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=52AE69DE.1000702@linux.vnet.ibm.com \
    --to=xiawenc@linux.vnet.ibm.com \
    --cc=eblake@redhat.com \
    --cc=jcody@redhat.com \
    --cc=kwolf@redhat.com \
    --cc=pbonzini@redhat.com \
    --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 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.