From: Kevin Wolf <kwolf@redhat.com>
To: Eric Blake <eblake@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 10:40:47 +0200 [thread overview]
Message-ID: <20180814084047.GD5025@dhcp-200-186.str.redhat.com> (raw)
In-Reply-To: <f6fcbd58-2462-d432-a038-cc13bb0dcf23@redhat.com>
Am 13.08.2018 um 20:19 hat Eric Blake geschrieben:
> On 08/13/2018 11:56 AM, Max Reitz wrote:
> >
> > Ah, hm, so much for that. Hm... I don't quite know what to think of
> > this. It does indeed improve legibility. But the question is whether
> > --help should be as condensed as possible, and if the user finds it hard
> > to read, whether they should not just open the man page...
> >
> > Then again, our --help text already has 102 lines.
> >
> > Let me just think about it for a bit longer. :-)
> > (And see whether others have opinions.)
>
> 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>.
$ qemu-img check --help
usage: qemu-img check [--object objectdef] [--image-opts] [-q] [-f fmt] [--output=ofmt] [-r [leaks | all]] [-T src_cache] [-U] filename
Command parameters:
-f 'fmt' is the disk image format. It is guessed automatically
in most cases.
-q use Quiet mode - do not print any output (except errors).
-r tries to repair any inconsistencies that are found during the
check. '-r leaks' repairs only cluster leaks, whereas '-r
all' fixes all kinds of errors, with a higher risk of
choosing the wrong fix or hiding corruption that has already
occurred.
-T 'src_cache' is the cache mode used to read input disk images,
the valid options are the same as for the 'cache' option.
--object 'objectdef' is a QEMU user creatable object definition. See
the qemu(1) manual page for a description of the object
properties. The most common object type is a 'secret', which
is used to supply passwords and/or encryption keys.
--output 'ofmt' is 'human' for human-readable output (default) or
'json' for JSON output.
Examples:
...
Kevin
next prev parent reply other threads:[~2018-08-14 8:40 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 [this message]
2018-08-14 12:55 ` Eric Blake
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=20180814084047.GD5025@dhcp-200-186.str.redhat.com \
--to=kwolf@redhat.com \
--cc=Qemu-devel@nongnu.org \
--cc=eblake@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).