From: Eric Blake <eblake@redhat.com>
To: Laurent Vivier <lvivier@redhat.com>,
qemu-devel@nongnu.org, marcandre.lureau@gmail.com
Subject: Re: [Qemu-devel] [PATCH v4 1/3] vl: Add a flags to define parameters with optional arguments.
Date: Fri, 4 Sep 2015 13:52:50 -0600 [thread overview]
Message-ID: <55E9F692.9000804@redhat.com> (raw)
In-Reply-To: <55E9F40E.4010705@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 577 bytes --]
On 09/04/2015 01:42 PM, Eric Blake wrote:
> On 09/04/2015 01:30 PM, Laurent Vivier wrote:
>> The goal is to be able to use '-help' alone, or with
>> a sub-section, i.e. '-help network,usb'.
>
> Uggh. I hate reinventing the wheel. We aren't using getopt_long_only();
> but if we were, the ONLY way to specify optional arguments to a long
> option is by using the = sign, and not by space separation.
Also, we tend to avoid trailing '.' in subject lines.
--
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:[~2015-09-04 19:52 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-04 19:30 [Qemu-devel] [PATCH v4 0/3] Improve -help Laurent Vivier
2015-09-04 19:30 ` [Qemu-devel] [PATCH v4 1/3] vl: Add a flags to define parameters with optional arguments Laurent Vivier
2015-09-04 19:42 ` Eric Blake
2015-09-04 19:52 ` Eric Blake [this message]
2015-09-04 19:55 ` Stefan Weil
2015-09-04 20:06 ` Eric Blake
2015-09-04 19:30 ` [Qemu-devel] [PATCH v4 2/3] help: fix typo Laurent Vivier
2015-09-04 19:34 ` Eric Blake
2015-09-06 11:06 ` Michael Tokarev
2015-09-04 19:30 ` [Qemu-devel] [PATCH v4 3/3] Use help sub-sections to create sub-help options Laurent Vivier
2015-09-04 20:13 ` Eric Blake
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=55E9F692.9000804@redhat.com \
--to=eblake@redhat.com \
--cc=lvivier@redhat.com \
--cc=marcandre.lureau@gmail.com \
--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 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).