All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kevin Wolf <kwolf@redhat.com>
To: Max Reitz <mreitz@redhat.com>
Cc: qemu-devel@nongnu.org, qemu-block@nongnu.org
Subject: Re: [Qemu-devel]  [PATCH 0/2] qemu-img.texi: Provide more info on some commands’ output
Date: Mon, 20 May 2019 15:32:36 +0200	[thread overview]
Message-ID: <20190520133236.GG5699@localhost.localdomain> (raw)
In-Reply-To: <20190515075917.24980-1-mreitz@redhat.com>

Am 15.05.2019 um 09:59 hat Max Reitz geschrieben:
> Most qemu-img subcommands that have (optional) JSON output don’t
> describe the structure of their JSON output -- but having a fixed,
> well-known output structure kind of is the point of having JSON output
> at all.  Therefore, patch 1 in this series makes every such command note
> which QAPI type their JSON output has in the qemu-img man page.  (The
> exception to this is the map subcommand, which does not emit a
> QAPI-typed object.  It already has a description of the structure of its
> output object, though.)
> 
> That should be enough to thoroughly explain the machine-readable output.
> But we can also do better for the human-readable output: qemu-img info
> emits quite a bit of information, and not all of it is self-explanatory.
> In patch 2, I’ve tried to provide some potentially missing explanation.

Thanks, applied to the block branch.

Kevin


      parent reply	other threads:[~2019-05-20 13:34 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-15  7:59 [Qemu-devel] [PATCH 0/2] qemu-img.texi: Provide more info on some commands’ output Max Reitz
2019-05-15  7:59 ` [Qemu-devel] [PATCH 1/2] qemu-img.texi: Be specific about JSON object types Max Reitz
2019-05-15  7:59 ` [Qemu-devel] [PATCH 2/2] qemu-img.texi: Describe human-readable info output Max Reitz
2019-05-20 13:32 ` Kevin Wolf [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=20190520133236.GG5699@localhost.localdomain \
    --to=kwolf@redhat.com \
    --cc=mreitz@redhat.com \
    --cc=qemu-block@nongnu.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.