From: Eric Blake <eblake@redhat.com>
To: Kevin Wolf <kwolf@redhat.com>
Cc: Max Reitz <mreitz@redhat.com>,
John Arbuckle <programmingkidx@gmail.com>,
qemu-block@nongnu.org, Qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] qemu-img.c: increase spacing between commands in documentation
Date: Tue, 14 Aug 2018 07:55:46 -0500 [thread overview]
Message-ID: <91ef77d7-026d-4930-bd4c-a94b17fa247c@redhat.com> (raw)
In-Reply-To: <20180814084047.GD5025@dhcp-200-186.str.redhat.com>
On 08/14/2018 03:40 AM, Kevin Wolf wrote:
>> And I've already expressed my opinion that it is already rather long, where
>> making it longer is not necessarily making it smarter.
>
> I think if we want to improve the help text, we should split it up.
>
> $ qemu-img --help
> qemu-img version 2.12.94 (v3.0.0-rc4-5-g4fe9c3e13d-dirty)
> Copyright (c) 2003-2017 Fabrice Bellard and the QEMU Project developers
> usage: qemu-img [standard options] command [command options]
> QEMU disk image utility
>
> '-h', '--help' display this help and exit
> '-V', '--version' output version information and exit
> '-T', '--trace' [[enable=]<pattern>][,events=<file>][,file=<file>]
> specify tracing options
>
> Commands:
>
> amend Change options of an existing disk image
> bench Run benchmarks on a given disk image
> check Check the disk image for consistency or repair it
> commit Merge the disk image into its backing file
> ...
>
> Run 'qemu-img <command> --help' for details.
>
> See <https://qemu.org/contribute/report-a-bug> for how to report bugs.
> More information on the QEMU project at <https://qemu.org>.
Indeed, that matches the approach that 'cvs --help' and 'git --help'
have taken. I could live with a split along those lines as being
something smarter. When you want to learn the options for 'create', you
may have to ask two different --help commands to learn everything you
need ['--help' didn't give me enough, but told me to use 'create
--help'], but at least you are not inundated with answers irrelevant to
the question you are asking, so you don't have to scroll through a wall
of text.
--
Eric Blake, Principal Software Engineer
Red Hat, Inc. +1-919-301-3266
Virtualization: qemu.org | libvirt.org
next prev parent reply other threads:[~2018-08-14 12:55 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20180730212249.16418-1-programmingkidx@gmail.com>
2018-07-31 0:55 ` [Qemu-devel] [PATCH] qemu-img.c: increase spacing between commands in documentation Programmingkid
2018-08-13 16:56 ` Max Reitz
2018-08-13 18:19 ` Eric Blake
2018-08-14 8:40 ` Kevin Wolf
2018-08-14 12:55 ` Eric Blake [this message]
2018-08-14 17:59 ` Programmingkid
2018-08-17 1:27 ` Programmingkid
2018-08-17 13:44 ` Eric Blake
2018-08-17 19:28 ` Programmingkid
2018-08-17 20:59 ` Eric Blake
2018-08-18 16:48 ` Programmingkid
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=91ef77d7-026d-4930-bd4c-a94b17fa247c@redhat.com \
--to=eblake@redhat.com \
--cc=Qemu-devel@nongnu.org \
--cc=kwolf@redhat.com \
--cc=mreitz@redhat.com \
--cc=programmingkidx@gmail.com \
--cc=qemu-block@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).