From: Markus Armbruster <armbru@redhat.com>
To: John Snow <jsnow@redhat.com>
Cc: qemu-devel@nongnu.org, qemu-block@nongnu.org,
"Kevin Wolf" <kwolf@redhat.com>,
"Philippe Mathieu-Daudé" <philmd@mailo.com>,
"Eric Blake" <eblake@redhat.com>,
"Jonathan Cameron" <jic23@kernel.org>,
"Lukas Straub" <lukasstraub2@web.de>,
"Paolo Bonzini" <pbonzini@redhat.com>,
"Zhao Liu" <zhao1.liu@intel.com>,
linux-cxl@vger.kernel.org, "Jason Wang" <jasowangio@gmail.com>,
"Hanna Reitz" <hreitz@redhat.com>,
"Fabiano Rosas" <farosas@suse.de>, "Peter Xu" <peterx@redhat.com>
Subject: Re: [PATCH 1/6] qapi: convert remaining simple intros for block-export.json
Date: Sat, 12 Sep 2026 09:34:26 +0200 [thread overview]
Message-ID: <87ik4a3ou5.fsf@pond.sub.org> (raw)
In-Reply-To: <20260911172200.227914-2-jsnow@redhat.com> (John Snow's message of "Fri, 11 Sep 2026 13:21:55 -0400")
John Snow <jsnow@redhat.com> writes:
> These are either structs or unions that are used in an inlinable
> context: i.e. the generated documentation is likely to feature a
> version of this documentation block that does not include the intro in
> context of another command, event, or structure.
>
> Signed-off-by: John Snow <jsnow@redhat.com>
> ---
> qapi/block-export.json | 19 ++++++++-----------
> 1 file changed, 8 insertions(+), 11 deletions(-)
>
> diff --git a/qapi/block-export.json b/qapi/block-export.json
> index 2893c6456d5..e9f7e72c8ee 100644
> --- a/qapi/block-export.json
> +++ b/qapi/block-export.json
> @@ -37,10 +37,9 @@
>
> ##
> # @NbdServerOptions:
> -#
> -# Keep this type consistent with the `NbdServerOptionsLegacy` type.
> -# The only intended difference is using `SocketAddress` instead of
> -# `SocketAddressLegacy`.
> +# Keep this type consistent with the `NbdServerOptionsLegacy`
> +# type. The only intended difference is using `SocketAddress`
> +# instead of `SocketAddressLegacy`.
"Keep this consistent" is for developers, and should not go into user
reference documentation.
Let's leave this for another day, just take note of future work:
6. Move comments for developers out of doc comments
> #
> # @addr: Address on which to listen (since 4.2).
> ##
> @@ -50,10 +49,9 @@
>
> ##
> # @NbdServerOptionsLegacy:
> -#
> -# Keep this type consistent with the `NbdServerOptions` type. The
> -# only intended difference is using `SocketAddressLegacy` instead of
> -# `SocketAddress`.
> +# Keep this type consistent with the `NbdServerOptions` type. The
> +# only intended difference is using `SocketAddressLegacy` instead
> +# of `SocketAddress`.
Likewise.
> #
> # @addr: Address on which to listen (since 1.3).
> ##
> @@ -339,9 +337,8 @@
>
> ##
> # @BlockExportOptions:
> -#
> -# Describes a block export, i.e. how single node should be exported on
> -# an external interface.
> +# Describes a block export, i.e. how single node should be
> +# exported on an external interface.
> #
> # @type: Block export type
> #
next prev parent reply other threads:[~2026-09-12 7:34 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-11 17:21 [PATCH 0/6] qapi: convert remaining "simple" intro sections John Snow
2026-09-11 17:21 ` [PATCH 1/6] qapi: convert remaining simple intros for block-export.json John Snow
2026-09-12 7:34 ` Markus Armbruster [this message]
2026-09-11 17:21 ` [PATCH 2/6] qapi: convert remaining simple intros for cxl.json John Snow
2026-09-11 17:21 ` [PATCH 3/6] qapi: convert remaining simple intros for machine.json John Snow
2026-09-12 7:34 ` Markus Armbruster
2026-09-11 17:21 ` [PATCH 4/6] qapi: convert remaining simple intros for block-core.json John Snow
2026-09-12 7:35 ` Markus Armbruster
2026-09-11 17:21 ` [PATCH 5/6] qapi: convert intro sections with "TODO" markers John Snow
2026-09-12 6:58 ` Markus Armbruster
2026-09-11 17:22 ` [PATCH 6/6] qapi: convert intro sections followed by notes/examples John Snow
2026-09-12 7:36 ` [PATCH 0/6] qapi: convert remaining "simple" intro sections 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=87ik4a3ou5.fsf@pond.sub.org \
--to=armbru@redhat.com \
--cc=eblake@redhat.com \
--cc=farosas@suse.de \
--cc=hreitz@redhat.com \
--cc=jasowangio@gmail.com \
--cc=jic23@kernel.org \
--cc=jsnow@redhat.com \
--cc=kwolf@redhat.com \
--cc=linux-cxl@vger.kernel.org \
--cc=lukasstraub2@web.de \
--cc=pbonzini@redhat.com \
--cc=peterx@redhat.com \
--cc=philmd@mailo.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox