From: Paolo Bonzini <pbonzini@redhat.com>
To: Laszlo Ersek <lersek@redhat.com>
Cc: kwolf@redhat.com, aliguori@amazon.com, mjt@tls.msk.ru,
armbru@redhat.com, qemu-devel@nongnu.org, mreitz@redhat.com,
stefanha@redhat.com, lcapitulino@redhat.com,
Igor Mammedov <imammedo@redhat.com>,
akong@redhat.com
Subject: Re: [Qemu-devel] [PATCH 2/2] vl: convert -m to QemuOpts
Date: Wed, 26 Feb 2014 14:45:01 +0100 [thread overview]
Message-ID: <530DEFDD.9060305@redhat.com> (raw)
In-Reply-To: <530DEF48.6060509@redhat.com>
Il 26/02/2014 14:42, Laszlo Ersek ha scritto:
> When you have a QemuOpt that takes an argument, then the documentation
> of the default behavior usually explains the case when the QemuOpt is
> present, and the argument is absent. The documentation of the default
> behavior usually doesn't concern the case when the QemuOpt*s* itself is
> absent. Cf.
>
> (1) -foo bar
> (2) -foo bar=baz
> (3) [nothing]
>
> The "default" in the docs tends to explain case (1), not case (3).
>
> In this case we have: -m [mem=]megs
>
> (1) -m mem -- makes no sense
> (2) -m mem=megs -- works, and well documented
> (3) [nothing] -- is what the proposed docs describe as "default", but it
> doesn't match "historical practice".
>
> (1) in general can make sense, eg. for booleans.
>
> Anyway I don't feel strongly about this in the least -- I just thought
> I'd point it out.
Yeah, you're right.
> Feel free to ignore it; I have no good suggestion as
> to how to make it consistent across all options.
Neither do I, but at least "megs" is not marked as an optional element,
so I think it's not that ambiguous.
Paolo
next prev parent reply other threads:[~2014-02-26 13:45 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-06 8:16 [Qemu-devel] [PATCH 0/2] convert -m to QemuOpts Igor Mammedov
2014-02-06 8:16 ` [Qemu-devel] [PATCH 1/2] QemuOpts: introduce qemu_find_opts_singleton Igor Mammedov
2014-02-10 17:00 ` Laszlo Ersek
2014-02-11 11:52 ` Igor Mammedov
2014-02-06 8:16 ` [Qemu-devel] [PATCH 2/2] vl: convert -m to QemuOpts Igor Mammedov
2014-02-10 17:38 ` Laszlo Ersek
2014-02-13 12:47 ` Igor Mammedov
2014-02-26 13:29 ` Paolo Bonzini
2014-02-26 13:42 ` Laszlo Ersek
2014-02-26 13:45 ` Paolo Bonzini [this message]
2014-02-26 13:50 ` Igor Mammedov
2014-02-26 14:00 ` Paolo Bonzini
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=530DEFDD.9060305@redhat.com \
--to=pbonzini@redhat.com \
--cc=akong@redhat.com \
--cc=aliguori@amazon.com \
--cc=armbru@redhat.com \
--cc=imammedo@redhat.com \
--cc=kwolf@redhat.com \
--cc=lcapitulino@redhat.com \
--cc=lersek@redhat.com \
--cc=mjt@tls.msk.ru \
--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.