From: Max Reitz <mreitz@redhat.com>
To: Eric Blake <eblake@redhat.com>, qemu-devel@nongnu.org
Cc: Kevin Wolf <kwolf@redhat.com>,
Markus Armbruster <armbru@redhat.com>,
Stefan Hajnoczi <stefanha@redhat.com>
Subject: Re: [Qemu-devel] [PATCH] qemu-img: Document check exit codes
Date: Mon, 02 Jun 2014 21:53:56 +0200 [thread overview]
Message-ID: <538CD654.70303@redhat.com> (raw)
In-Reply-To: <538CD46D.1060905@redhat.com>
On 02.06.2014 21:45, Eric Blake wrote:
> On 06/02/2014 01:31 PM, Max Reitz wrote:
>> The exit code 63 (check not supported by image format) was not even
>> documented in the comment above the check command in the source code;
>> add it, as it does indeed seem useful.
>>
>> Also, document all of check's exit codes in the manpage.
>>
>> Signed-off-by: Max Reitz <mreitz@redhat.com>
>> Reported-by: Markus Armbruster <armbru@redhat.com>
>> ---
>> qemu-img.c | 9 +++++----
>> qemu-img.texi | 23 +++++++++++++++++++++++
>> 2 files changed, 28 insertions(+), 4 deletions(-)
>>
>> +In case the image does not have any inconsistencies, check exits with @code{0}.
>> +Other exit codes indicate the kind of inconsistency found or if another error
>> +occured. The following table summarizes all exit codes of the check subcommand:
> s/occured/occurred/
It's a bit embarrassing that the correct spelling was even part of the
hunk environment. :-)
>> +
>> +If @code{-r} is specified, exit codes representing the image state refer to the
>> +state after (the attempt on) repairing it. That is, a successful @code{-r all}
> Not sure if this reads better, but:
Yes, the sentence is kind of hard to read, but I couldn't think of a
nicer expression (I could drop the "representing the image state" part,
but then people might ask how this applies to code 63 -- but then again,
it just doesn't make any sense for that code, so...). That's why I added
the explanatory example following it.
> s/attempt on/attempt at/
>
> With the spelling fix,
> Reviewed-by: Eric Blake <eblake@redhat.com>
Thank you,
Max
prev parent reply other threads:[~2014-06-02 19:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-02 19:31 [Qemu-devel] [PATCH] qemu-img: Document check exit codes Max Reitz
2014-06-02 19:45 ` Eric Blake
2014-06-02 19:53 ` Max Reitz [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=538CD654.70303@redhat.com \
--to=mreitz@redhat.com \
--cc=armbru@redhat.com \
--cc=eblake@redhat.com \
--cc=kwolf@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@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).