From: Markus Armbruster <armbru@redhat.com>
To: John Snow <jsnow@redhat.com>
Cc: qemu-devel@nongnu.org, "Laurent Vivier" <laurent@vivier.eu>,
"Kostiantyn Kostiuk" <kkostiuk@redhat.com>,
"Michael S. Tsirkin" <mst@redhat.com>,
"Zhao Liu" <zhao1.liu@intel.com>,
"Michael Roth" <michael.roth@amd.com>,
"Pierrick Bouvier" <pierrick.bouvier@oss.qualcomm.com>,
"Daniel P. Berrangé" <berrange@redhat.com>,
"Jason Wang" <jasowangio@gmail.com>,
qemu-trivial@nongnu.org,
"Philippe Mathieu-Daudé" <philmd@oss.qualcomm.com>,
"Stefano Garzarella" <sgarzare@redhat.com>,
"Kashyap Chamarthy" <kchamart@redhat.com>,
"Eric Blake" <eblake@redhat.com>,
"Hanna Reitz" <hreitz@redhat.com>,
"Kevin Wolf" <kwolf@redhat.com>,
qemu-block@nongnu.org, "Michael Tokarev" <mjt@tls.msk.ru>
Subject: Re: [PATCH v2 5/8] qapi: split intros at natural cutoff points for qga/qapi-schema.json
Date: Wed, 23 Sep 2026 08:25:40 +0200 [thread overview]
Message-ID: <87h5jgzdp7.fsf@pond.sub.org> (raw)
In-Reply-To: <20260922205605.501602-6-jsnow@redhat.com> (John Snow's message of "Tue, 22 Sep 2026 16:56:02 -0400")
John Snow <jsnow@redhat.com> writes:
> Note that these intro conversions introduce a new intro/details split
> point. This new split point may or may not change the rendered output
> depending on if any documentation is auto-generated and inserted for
> this definition.
>
> This has tangible effects on how @guest-fsfreeze-status documentation
> is rendered, while the other two appear unchanged.
Doesn't say how it changes, and it's not visible in the patch. Suggest
How @guest-fsfreeze-status documentation is rendered improves
slightly: "Note:" moves from above "Return" to below. The other
conversions don't change rendered documentation.
>
> Signed-off-by: John Snow <jsnow@redhat.com>
next prev parent reply other threads:[~2026-09-23 6:26 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-22 20:55 [PATCH v2 0/8] qapi: convert intros for qga, firmware, etc John Snow
2026-09-22 20:55 ` [PATCH v2 1/8] qapi: convert/split remaining qapi/qmp intro sections John Snow
2026-09-22 20:55 ` [PATCH v2 2/8] qapi: convert intro sections for unit tests John Snow
2026-09-23 6:07 ` Markus Armbruster
2026-09-23 17:17 ` John Snow
2026-09-22 20:56 ` [PATCH v2 3/8] qapi: convert trivial intros for qga/qapi-schema.json John Snow
2026-09-22 20:56 ` [PATCH v2 4/8] qapi: convert simple " John Snow
2026-09-22 20:56 ` [PATCH v2 5/8] qapi: split intros at natural cutoff points " John Snow
2026-09-23 6:25 ` Markus Armbruster [this message]
2026-09-23 17:18 ` John Snow
2026-09-22 20:56 ` [PATCH v2 6/8] qapi: split intros " John Snow
2026-09-22 20:56 ` [PATCH v2 7/8] qapi: convert intro sections for docs/interop/firmware.json John Snow
2026-09-22 20:56 ` [PATCH v2 8/8] qapi: convert intro sections for docs/interop/vhost-user.json John Snow
2026-09-23 6:45 ` [PATCH v2 0/8] qapi: convert intros for qga, firmware, etc Markus Armbruster
2026-09-23 6:49 ` Markus Armbruster
2026-09-23 17:19 ` John Snow
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=87h5jgzdp7.fsf@pond.sub.org \
--to=armbru@redhat.com \
--cc=berrange@redhat.com \
--cc=eblake@redhat.com \
--cc=hreitz@redhat.com \
--cc=jasowangio@gmail.com \
--cc=jsnow@redhat.com \
--cc=kchamart@redhat.com \
--cc=kkostiuk@redhat.com \
--cc=kwolf@redhat.com \
--cc=laurent@vivier.eu \
--cc=michael.roth@amd.com \
--cc=mjt@tls.msk.ru \
--cc=mst@redhat.com \
--cc=philmd@oss.qualcomm.com \
--cc=pierrick.bouvier@oss.qualcomm.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu-trivial@nongnu.org \
--cc=sgarzare@redhat.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.