qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Thomas Huth <thuth@redhat.com>
To: "Daniel P. Berrange" <berrange@redhat.com>,
	Eric Blake <eblake@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:41:09 +0100	[thread overview]
Message-ID: <54f33ad4-4483-9f92-ff24-9e6d1f4daf2a@redhat.com> (raw)
In-Reply-To: <20171212141749.GC26971@redhat.com>

On 12.12.2017 15:17, Daniel P. Berrange wrote:
> On Fri, Dec 08, 2017 at 10:16:50AM -0600, Eric Blake wrote:
>> On 12/08/2017 05:58 AM, Daniel P. Berrange wrote:
[...]
>>> +
>>> +@node tls_creds_setup
>>> +@subsection TLS x509 credential configuration
>>> +
>>> +QEMU has a standard mechanism for loading x509 credentials that will be
>>> +used for network services and clients. It requires specifying the
>>> +@code{tls-creds-x509} class name to the @code{-object} command line
>>> +argument for the system emulators. This also works for the helper tools
>>> +like @code{qemu-nbd} and @code{qemu-img}, but is named @code{--object}.
>>
>> 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!

... and maybe we could also introduce some more short options for the
most popular parameters one day? A short option for "--device" would be
really handy, for example.

 Thomas

  reply	other threads:[~2017-12-14  9:41 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 [this message]
2017-12-14 16:48       ` 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=54f33ad4-4483-9f92-ff24-9e6d1f4daf2a@redhat.com \
    --to=thuth@redhat.com \
    --cc=berrange@redhat.com \
    --cc=eblake@redhat.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).