From: Markus Armbruster <armbru@redhat.com>
To: John Snow <jsnow@redhat.com>
Cc: qemu-devel <qemu-devel@nongnu.org>,
"Igor Mammedov" <imammedo@redhat.com>,
"Mauro Carvalho Chehab" <mchehab+huawei@kernel.org>,
"Michael S. Tsirkin" <mst@redhat.com>,
"Michael Roth" <michael.roth@amd.com>,
"Ani Sinha" <anisinha@redhat.com>,
"Gerd Hoffmann" <kraxel@redhat.com>,
"Eric Blake" <eblake@redhat.com>,
"Pierrick Bouvier" <pierrick.bouvier@oss.qualcomm.com>,
"Philippe Mathieu-Daudé" <philmd@linaro.org>,
"Marc-André Lureau" <marcandre.lureau@redhat.com>,
"Richard Henderson" <richard.henderson@linaro.org>,
"Paolo Bonzini" <pbonzini@redhat.com>,
"Peter Maydell" <peter.maydell@linaro.org>
Subject: Re: [PATCH 00/12] qapi: add formal "intro" section
Date: Fri, 24 Apr 2026 15:37:01 +0200 [thread overview]
Message-ID: <87v7dgpjia.fsf@pond.sub.org> (raw)
In-Reply-To: <CAFn=p-ZNOYwSybMQDHnw9FF88_RDaRNhJkFjCT3AHKu496Ggeg@mail.gmail.com> (John Snow's message of "Fri, 24 Apr 2026 08:52:21 -0400")
John Snow <jsnow@redhat.com> writes:
> On Fri, Apr 24, 2026, 8:50 AM Markus Armbruster <armbru@redhat.com> wrote:
>
>> John Snow <jsnow@redhat.com> writes:
>>
>> > Hiya, this is a series that explores a potential syntax for a
>> > designated "Intro" section. Markus knows why I want this, but for
>> > everyone else: a designated "Introduction" section is useful for the
>> > desired "inliner" feature for the new QAPI doc system. Commits explain
>> > a bit more. This is prep work and doesn't really change anything
>> > tangibly except source code syntax for the QAPI docs.
[...]
>> Why not wholesale conversion? As long as generated output stays the
>> same. It does in this series, except for harmless line breaks.
>>
>
> When we last spoke, we weren't convinced this was the right approach and we
> both wanted to see it. So I did enough to get a taste.
Yes, and it makes sense.
>> > This series demonstrates conversion of just four modules; if I'm given
>> > a thumbs up, I will convert the rest of QAPI, one module (or
>> > maintainer stanza) per patch like how I handled adding
>> > cross-references.
next prev parent reply other threads:[~2026-04-24 13:38 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-23 22:00 [PATCH 00/12] qapi: add formal "intro" section John Snow
2026-04-23 22:00 ` [PATCH 01/12] tests/qapi: generate output in source order John Snow
2026-04-23 22:00 ` [PATCH 02/12] qapi/docs: remove unused QAPIDoc subsection members John Snow
2026-04-23 22:00 ` [PATCH 03/12] qapi/docs: make remaining subsection members "private" John Snow
2026-04-23 22:00 ` [PATCH 04/12] qapi/docs: add "Intro" section John Snow
2026-04-23 22:00 ` [PATCH 05/12] qapi/docs: adjust stub member insertion algorithm John Snow
2026-04-23 22:00 ` [PATCH 06/12] qapi/docs: remove implicit Plain section John Snow
2026-04-23 22:00 ` [PATCH 07/12] qapi/docs: add "Intro" section parsing John Snow
2026-04-23 22:00 ` [PATCH 08/12] qapi/docs: Add rendering for INTRO sections John Snow
2026-04-23 22:00 ` [PATCH 09/12] qapi: convert intro sections for accelerator.json John Snow
2026-04-23 22:00 ` [PATCH 10/12] qapi: convert intro sections for acpi-hest.json John Snow
2026-04-23 22:00 ` [PATCH 11/12] qapi: convert intro sections for acpi.json John Snow
2026-04-23 22:00 ` [PATCH 12/12] qapi: convert intro sections for audio.json John Snow
2026-04-24 12:50 ` [PATCH 00/12] qapi: add formal "intro" section Markus Armbruster
2026-04-24 12:52 ` John Snow
2026-04-24 13:37 ` Markus Armbruster [this message]
2026-04-24 19:19 ` John Snow
2026-04-28 11:45 ` 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=87v7dgpjia.fsf@pond.sub.org \
--to=armbru@redhat.com \
--cc=anisinha@redhat.com \
--cc=eblake@redhat.com \
--cc=imammedo@redhat.com \
--cc=jsnow@redhat.com \
--cc=kraxel@redhat.com \
--cc=marcandre.lureau@redhat.com \
--cc=mchehab+huawei@kernel.org \
--cc=michael.roth@amd.com \
--cc=mst@redhat.com \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=philmd@linaro.org \
--cc=pierrick.bouvier@oss.qualcomm.com \
--cc=qemu-devel@nongnu.org \
--cc=richard.henderson@linaro.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.