All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eric Blake <eblake@redhat.com>
To: Kevin Wolf <kwolf@redhat.com>, qemu-devel@nongnu.org
Cc: stefanha@redhat.com, mreitz@redhat.com
Subject: Re: [Qemu-devel] [PATCH 1/7] qemu-img create: Detect options specified more than once
Date: Wed, 19 Feb 2014 09:38:50 -0700	[thread overview]
Message-ID: <5304DE1A.8040300@redhat.com> (raw)
In-Reply-To: <1392822778-4823-2-git-send-email-kwolf@redhat.com>

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

On 02/19/2014 08:12 AM, Kevin Wolf wrote:
> If you specified multiple -o options for qemu-img create, it would
> silently ignore all but the last one. Similarly, for other options the
> last occurence wins (which is at least a bit less surprising). Error out

s/occurence/occurrence/

> instead.

For other options, erroring out is okay.  But for -o, I would prefer if
we could concatenate multiple -o as if they had been passed in one
larger -o, rather than erroring out.  That is, I'd rather treat:

-o backing_file=/path/to/foo -o backing_fmt=qcow2

as a synonym of

-o backing_file=/path/to/foo,backing_fmt=qcow2

> 
> The only exception is a -o help option, which may be added to any valid
> qemu-img create command and ignores all other options.

If you consider my above request for concatenating multiple -o options,
rather than rejecting duplicates, then that means:

-o backing_file=/path/to/foo,help

would have to do the right thing about displaying help.

I also have the complaint that:

qemu-img create -o help -f qcow2

does not tell me the qcow2 specific options; I have to do something like:

qemu-img create -o help -f qcow2 /dev/null

It would be nice if we could make -o help smarter so that it no longer
requires the presence of a file name (probably a separate patch).

In other words, I like that your series is trying to improve things, but
I don't think it is making the right improvement.

-- 
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 --]

  parent reply	other threads:[~2014-02-19 16:39 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-19 15:12 [Qemu-devel] [PATCH 0/7] qemu-img: Fix handling of multiply specified options Kevin Wolf
2014-02-19 15:12 ` [Qemu-devel] [PATCH 1/7] qemu-img create: Detect options specified more than once Kevin Wolf
2014-02-19 16:05   ` Fam Zheng
2014-02-19 16:38   ` Eric Blake [this message]
2014-02-19 15:12 ` [Qemu-devel] [PATCH 2/7] qemu-img convert: " Kevin Wolf
2014-02-19 15:12 ` [Qemu-devel] [PATCH 3/7] qemu-img amend: " Kevin Wolf
2014-02-19 15:12 ` [Qemu-devel] [PATCH 4/7] qemu-img: " Kevin Wolf
2014-02-19 15:12 ` [Qemu-devel] [PATCH 5/7] qemu-img create: Support multiple -o options Kevin Wolf
2014-02-19 16:18   ` Fam Zheng
2014-02-19 16:46   ` Eric Blake
2014-02-19 15:12 ` [Qemu-devel] [PATCH 6/7] qemu-img convert: " Kevin Wolf
2014-02-19 15:12 ` [Qemu-devel] [PATCH 7/7] qemu-img amend: " Kevin Wolf
2014-02-20  7:18 ` [Qemu-devel] [PATCH 0/7] qemu-img: Fix handling of multiply specified options Markus Armbruster
2014-02-20  9:03   ` Kevin Wolf
2014-02-20  9:48     ` Markus Armbruster

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=5304DE1A.8040300@redhat.com \
    --to=eblake@redhat.com \
    --cc=kwolf@redhat.com \
    --cc=mreitz@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.