All of lore.kernel.org
 help / color / mirror / Atom feed
From: Markus Armbruster <armbru@redhat.com>
To: John Snow <jsnow@redhat.com>
Cc: qemu-devel@nongnu.org,
	"Marc-André Lureau" <marcandre.lureau@redhat.com>,
	"Michael S. Tsirkin" <mst@redhat.com>,
	"Eduardo Habkost" <eduardo@habkost.net>,
	"Jiri Pirko" <jiri@resnulli.us>,
	"Peter Maydell" <peter.maydell@linaro.org>,
	"Ani Sinha" <anisinha@redhat.com>,
	"Zhao Liu" <zhao1.liu@intel.com>, "Peter Xu" <peterx@redhat.com>,
	"Gerd Hoffmann" <kraxel@redhat.com>,
	"Fabiano Rosas" <farosas@suse.de>,
	qemu-block@nongnu.org, "Gonglei (Arei)" <arei.gonglei@huawei.com>,
	"Laurent Vivier" <laurent@vivier.eu>,
	"Jason Wang" <jasowang@redhat.com>,
	"Yanan Wang" <wangyanan55@huawei.com>,
	qemu-trivial@nongnu.org, "Stefan Hajnoczi" <stefanha@redhat.com>,
	"Mads Ynddal" <mads@ynddal.dk>,
	"Lukas Straub" <lukasstraub2@web.de>,
	"Marcel Apfelbaum" <marcel.apfelbaum@gmail.com>,
	"Kevin Wolf" <kwolf@redhat.com>,
	"Vladimir Sementsov-Ogievskiy" <vsementsov@yandex-team.ru>,
	"Michael Tokarev" <mjt@tls.msk.ru>,
	"Paolo Bonzini" <pbonzini@redhat.com>,
	"Daniel P. Berrangé" <berrange@redhat.com>,
	"Eric Blake" <eblake@redhat.com>,
	"Hanna Reitz" <hreitz@redhat.com>,
	"Zhenwei Pi" <pizhenwei@bytedance.com>,
	"Stefan Berger" <stefanb@linux.vnet.ibm.com>,
	"Michael Roth" <michael.roth@amd.com>,
	"Philippe Mathieu-Daudé" <philmd@linaro.org>
Subject: Re: [PATCH v6 4/4] qapi: rephrase return docs to avoid type name
Date: Fri, 11 Jul 2025 15:55:48 +0200	[thread overview]
Message-ID: <877c0eygpn.fsf@pond.sub.org> (raw)
In-Reply-To: <20250711051045.51110-5-jsnow@redhat.com> (John Snow's message of "Fri, 11 Jul 2025 01:10:45 -0400")

John Snow <jsnow@redhat.com> writes:

> Well, I tried. Maybe not very hard. Sorry!

Recommend to explain *why* we want to avoid the type name.

  "Returns: <description>" is rendered like "Return: <Type> –
  <description>".  Mentioning the type in the description again is
  commonly redundant.  Rephrase such descriptions not to.

> Signed-off-by: John Snow <jsnow@redhat.com>
> ---
>  qapi/block-core.json   | 6 +++---
>  qapi/block-export.json | 2 +-
>  qapi/block.json        | 2 +-
>  qapi/control.json      | 5 ++---
>  qapi/dump.json         | 5 ++---
>  qapi/introspect.json   | 6 +++---
>  qapi/job.json          | 2 +-
>  qapi/misc-i386.json    | 2 +-
>  qapi/misc.json         | 5 ++---
>  qapi/net.json          | 2 +-
>  qapi/pci.json          | 2 +-
>  qapi/qdev.json         | 3 +--
>  qapi/qom.json          | 8 +++-----
>  qapi/stats.json        | 2 +-
>  qapi/trace.json        | 2 +-
>  qapi/ui.json           | 2 +-
>  qapi/virtio.json       | 6 +++---
>  17 files changed, 28 insertions(+), 34 deletions(-)
>
> diff --git a/qapi/block-core.json b/qapi/block-core.json
> index d64f482d9bd..f18db3149a3 100644
> --- a/qapi/block-core.json
> +++ b/qapi/block-core.json
> @@ -763,7 +763,7 @@
>  #
>  # Get a list of BlockInfo for all virtual block devices.

Mentioning the type in the intro is commonly just as redundant as in
Returns:.

>  #
> -# Returns: a list of @BlockInfo describing each virtual block device.
> +# Returns: a list describing each virtual block device.

"A list" is arguably just as redundant as the list's element type.

The entire line is pretty redundant with the intro.

>  #     Filter nodes that were created implicitly are skipped over.
>  #
>  # Since: 0.14
> @@ -1168,7 +1168,7 @@
   ##
   # @query-blockstats:
   #
   # Query the `BlockStats` for all virtual block devices.
   #
   # @query-nodes: If true, the command will query all the block nodes
   #     that have a node name, in a list which will include "parent"
   #     information, but not "backing".  If false or omitted, the
   #     behavior is as before - query all the device backends,
   #     recursively including their "parent" and "backing".  Filter
>  #     nodes that were created implicitly are skipped over in this
>  #     mode.  (Since 2.3)
>  #
> -# Returns: A list of @BlockStats for each virtual block devices.
> +# Returns: A list of statistics for each virtual block device.

Again, the entire line is pretty redundant with the intro.

>  #
>  # Since: 0.14
>  #
> @@ -1440,7 +1440,7 @@
>  #
>  # Return information about long-running block device operations.
>  #
> -# Returns: a list of @BlockJobInfo for each active block job
> +# Returns: a list of job info for each active block job

Best not to abbreviate "information" to "info".

>  #
>  # Since: 1.1
>  ##

I need to stop here to take care of another series.  Gut feeling so far:
right direction, doesn't go far enough.

Choices:

* Go far enough.  Too close to the freeze for that, I'm afraid.

* Merge it basically as is, come back later to finish the job.

* Drop it for now, adjust your "QAPI: add cross-references to qapi docs"
  to enclose the type names not removed in `backquotes`.

Thoughts?

[...]



  reply	other threads:[~2025-07-11 13:56 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-11  5:10 [PATCH v6 0/4] qapi: add auto-generated return docs John Snow
2025-07-11  5:10 ` [PATCH v6 1/4] docs/qapi-domain: add return-nodesc John Snow
2025-07-11 17:22   ` Markus Armbruster
2025-07-11  5:10 ` [PATCH v6 2/4] docs, qapi: generate undocumented return sections John Snow
2025-07-11 13:22   ` Markus Armbruster
2025-07-11  5:10 ` [PATCH v6 3/4] qapi: remove trivial "Returns:" sections John Snow
2025-07-11 13:23   ` Markus Armbruster
2025-07-11  5:10 ` [PATCH v6 4/4] qapi: rephrase return docs to avoid type name John Snow
2025-07-11 13:55   ` Markus Armbruster [this message]
2025-07-14  6:40     ` Markus Armbruster
2025-07-14 13:40 ` [PATCH v6 0/4] qapi: add auto-generated return docs Markus Armbruster

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=877c0eygpn.fsf@pond.sub.org \
    --to=armbru@redhat.com \
    --cc=anisinha@redhat.com \
    --cc=arei.gonglei@huawei.com \
    --cc=berrange@redhat.com \
    --cc=eblake@redhat.com \
    --cc=eduardo@habkost.net \
    --cc=farosas@suse.de \
    --cc=hreitz@redhat.com \
    --cc=jasowang@redhat.com \
    --cc=jiri@resnulli.us \
    --cc=jsnow@redhat.com \
    --cc=kraxel@redhat.com \
    --cc=kwolf@redhat.com \
    --cc=laurent@vivier.eu \
    --cc=lukasstraub2@web.de \
    --cc=mads@ynddal.dk \
    --cc=marcandre.lureau@redhat.com \
    --cc=marcel.apfelbaum@gmail.com \
    --cc=michael.roth@amd.com \
    --cc=mjt@tls.msk.ru \
    --cc=mst@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=peter.maydell@linaro.org \
    --cc=peterx@redhat.com \
    --cc=philmd@linaro.org \
    --cc=pizhenwei@bytedance.com \
    --cc=qemu-block@nongnu.org \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-trivial@nongnu.org \
    --cc=stefanb@linux.vnet.ibm.com \
    --cc=stefanha@redhat.com \
    --cc=vsementsov@yandex-team.ru \
    --cc=wangyanan55@huawei.com \
    --cc=zhao1.liu@intel.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 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.