From: Eric Blake <eblake@redhat.com>
To: Thomas Huth <thuth@redhat.com>,
"Daniel P. Berrange" <berrange@redhat.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] docs: update information for TLS certificate management
Date: Thu, 14 Dec 2017 10:48:51 -0600 [thread overview]
Message-ID: <853f8f0b-453c-82c9-5e05-ccab21c41ad2@redhat.com> (raw)
In-Reply-To: <54f33ad4-4483-9f92-ff24-9e6d1f4daf2a@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 822 bytes --]
On 12/14/2017 03:41 AM, Thomas Huth wrote:
>>> You can use '--object' with qemu as well (getopt_long_only() accepts
>>> double-dash form in addition to single dash). If it makes it any easier
>>> to only document the double-dash form, then go for it.
>>
>> Since the QEMU -help text only mentions the single dash format, I'll
>> stick with that.
>>
>> Perhaps though, we should change the -help text (and all docs) to always
>> use double dash format so we're consistent across QEMU codebase, and more
>> normal CLI arg syntax for long options ?
>
> Good idea!
>
I've added it to
https://wiki.qemu.org/Contribute/BiteSizedTasks#Consistent_option_usage_in_documentation
--
Eric Blake, Principal Software Engineer
Red Hat, Inc. +1-919-301-3266
Virtualization: qemu.org | libvirt.org
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 619 bytes --]
prev parent reply other threads:[~2017-12-14 16:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-08 11:58 [Qemu-devel] [PATCH] docs: update information for TLS certificate management Daniel P. Berrange
2017-12-08 16:16 ` Eric Blake
2017-12-12 14:17 ` Daniel P. Berrange
2017-12-14 9:41 ` Thomas Huth
2017-12-14 16:48 ` Eric Blake [this message]
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=853f8f0b-453c-82c9-5e05-ccab21c41ad2@redhat.com \
--to=eblake@redhat.com \
--cc=berrange@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=thuth@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).