qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: Thomas Huth <thuth@redhat.com>,
	BALATON Zoltan <balaton@eik.bme.hu>,
	qemu-devel@nongnu.org, qemu-trivial@nongnu.org
Cc: "Michael S. Tsirkin" <mst@redhat.com>, Eric Blake <eblake@redhat.com>
Subject: Re: [Qemu-devel] [PATCH] Document command line options with single dash
Date: Tue, 17 Jul 2018 13:00:20 +0200	[thread overview]
Message-ID: <38d43770-ecc6-8ba0-0eab-34ca31c2ce7c@redhat.com> (raw)
In-Reply-To: <2164ddc5-68be-ffa2-cebf-6980220b1238@redhat.com>

On 17/07/2018 09:43, Thomas Huth wrote:
> On 16.07.2018 21:12, BALATON Zoltan wrote:
>> QEMU options have a single dash (but also work as double dash for
>> convenience and compatibility). Most options are listed with single
>> dash in command line help but some were listed with two dashes.
>> Normalize these to have the same format as the others.
>>
>> Left --preconfig as that is mentioned as double dash everywhere so I
>> assume that is the preferred form for that.
>>
>> Signed-off-by: BALATON Zoltan <balaton@eik.bme.hu>
>> ---
>>  qemu-options.hx | 8 ++++----
>>  1 file changed, 4 insertions(+), 4 deletions(-)
>>
>> diff --git a/qemu-options.hx b/qemu-options.hx
>> index 371c427..b1bf0f4 100644
>> --- a/qemu-options.hx
>> +++ b/qemu-options.hx
>> @@ -471,7 +471,7 @@ STEXI
>>  @item -balloon virtio[,addr=@var{addr}]
>>  @findex -balloon
>>  Enable virtio balloon device, optionally with PCI address @var{addr}. This
>> -option is deprecated, use @option{--device virtio-balloon} instead.
>> +option is deprecated, use @option{-device virtio-balloon} instead.
>>  ETEXI
>>  
>>  DEF("device", HAS_ARG, QEMU_OPTION_device,
>> @@ -2005,7 +2005,7 @@ DEF("netdev", HAS_ARG, QEMU_OPTION_netdev,
>>      "-netdev hubport,id=str,hubid=n[,netdev=nd]\n"
>>      "                configure a hub port on the hub with ID 'n'\n", QEMU_ARCH_ALL)
>>  DEF("nic", HAS_ARG, QEMU_OPTION_nic,
>> -    "--nic [tap|bridge|"
>> +    "-nic [tap|bridge|"
>>  #ifdef CONFIG_SLIRP
>>      "user|"
>>  #endif
>> @@ -2024,7 +2024,7 @@ DEF("nic", HAS_ARG, QEMU_OPTION_nic,
>>      "socket][,option][,...][mac=macaddr]\n"
>>      "                initialize an on-board / default host NIC (using MAC address\n"
>>      "                macaddr) and connect it to the given host network backend\n"
>> -    "--nic none      use it alone to have zero network devices (the default is to\n"
>> +    "-nic none       use it alone to have zero network devices (the default is to\n"
>>      "                provided a 'user' network connection)\n",
>>      QEMU_ARCH_ALL)
>>  DEF("net", HAS_ARG, QEMU_OPTION_net,
>> @@ -3339,7 +3339,7 @@ mlocking qemu and guest memory can be enabled via @option{mlock=on}
>>  ETEXI
>>  
>>  DEF("overcommit", HAS_ARG, QEMU_OPTION_overcommit,
>> -    "--overcommit [mem-lock=on|off][cpu-pm=on|off]\n"
>> +    "-overcommit [mem-lock=on|off][cpu-pm=on|off]\n"
>>      "                run qemu with overcommit hints\n"
>>      "                mem-lock=on|off controls memory lock support (default: off)\n"
>>      "                cpu-pm=on|off controls cpu power management (default: off)\n",
>>
> 
> Acked-by: Thomas Huth <thuth@redhat.com>
> 
> ... I'm in favour for consistency for the 3.0 release. But in the long
> run, we should really come to a conclusion what we prefer (we still got
> the double dash task at
> https://wiki.qemu.org/BiteSizedTasks#Consistent_option_usage_in_documentation
> )
> 

Queued, thanks.

Paolo

      reply	other threads:[~2018-07-17 11:00 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-16 19:12 [Qemu-devel] [PATCH] Document command line options with single dash BALATON Zoltan
2018-07-17  7:43 ` Thomas Huth
2018-07-17 11:00   ` Paolo Bonzini [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=38d43770-ecc6-8ba0-0eab-34ca31c2ce7c@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=balaton@eik.bme.hu \
    --cc=eblake@redhat.com \
    --cc=mst@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-trivial@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).