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,
	 Pierrick Bouvier <pierrick.bouvier@oss.qualcomm.com>,
	 Michael Roth <michael.roth@amd.com>
Subject: Re: [PATCH 05/11] docs/qapi-code-gen: add "Details" docs subsection
Date: Tue, 06 Oct 2026 10:36:28 +0200	[thread overview]
Message-ID: <87cxtndy43.fsf@pond.sub.org> (raw)
In-Reply-To: <20261001172239.2825745-6-jsnow@redhat.com> (John Snow's message of "Thu, 1 Oct 2026 13:22:32 -0400")

John Snow <jsnow@redhat.com> writes:

> Mostly, this is just adding a heading and explaining that arbitrary
> rST formatting is allowed in this section.
>
> Note: The QAPI parser still refers to these sections internally as
> "PLAIN",

Really?

>          but I wanted to name this documentation section after the
> eventual, true name for the section. It is effectively only an
> implementation detail at this point.
>
> Signed-off-by: John Snow <jsnow@redhat.com>
> ---
>  docs/devel/qapi-code-gen.rst | 11 +++++++++--
>  1 file changed, 9 insertions(+), 2 deletions(-)
>
> diff --git a/docs/devel/qapi-code-gen.rst b/docs/devel/qapi-code-gen.rst
> index fcb52ce157e..8fc75488019 100644
> --- a/docs/devel/qapi-code-gen.rst
> +++ b/docs/devel/qapi-code-gen.rst
> @@ -1035,8 +1035,15 @@ detailing a relevant error condition.  For example::
>   #     - Any other error returns a GenericError.
>  
>  
> -In other sections, the text is formatted, and rST markup can be
> -used.
> +Details
> +^^^^^^^
> +
> +Details sections are comprised of one or more paragraphs of rST
> +formatted text, but otherwise are not marked up with any QAPI-specific
> +syntax.

Feels awkward.  You're trying to define you're talking about, but what
you're talking about is distinguished by absence of syntax, which makes
it harder to nail down.

I can't see how to do this better right now.  I'll come back to it.

>          In general, this text contains in-depth explanations of the
> +definition being documented and may include various rST admonitions
> +like ``.. seealso::``, ``.. note::``, etc. This is also the section
> +where QMP usage examples should be placed.
>  
>  QMP Examples can be added by using the ``.. qmp-example::`` directive.
>  In its simplest form, this can be used to contain a single QMP code



  reply	other threads:[~2026-10-07  9:10 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-01 17:22 [PATCH 00/11] docs/qapi: revise and expand QAPI documentation spec John Snow
2026-10-01 17:22 ` [PATCH 01/11] docs/qapi-code-gen: change "x.y.z" to "x.y" for Since: documentation John Snow
2026-10-06  5:58   ` Markus Armbruster
2026-10-01 17:22 ` [PATCH 02/11] docs/qapi-code-gen: add "Putting it all together" subsection John Snow
2026-10-06  7:55   ` Markus Armbruster
2026-10-01 17:22 ` [PATCH 03/11] docs/qapi-code-gen: add "TODO" subsection John Snow
2026-10-06  8:02   ` Markus Armbruster
2026-10-01 17:22 ` [PATCH 04/11] docs/qapi-code-gen: add "Since" subsection John Snow
2026-10-01 17:22 ` [PATCH 05/11] docs/qapi-code-gen: add "Details" docs subsection John Snow
2026-10-06  8:36   ` Markus Armbruster [this message]
2026-10-01 17:22 ` [PATCH 06/11] docs/qapi-code-gen: add "Errors" and "Returns" subsections John Snow
2026-10-01 17:22 ` [PATCH 07/11] docs/qapi-code-gen: add "Tagged sections" subsection John Snow
2026-10-01 17:22 ` [PATCH 08/11] docs/qapi-code-gen: add "Descriptions" subsection John Snow
2026-10-06  9:08   ` Markus Armbruster
2026-10-01 17:22 ` [PATCH 09/11] docs/qapi-code-gen: add "Feature descriptions" subsection John Snow
2026-10-01 17:22 ` [PATCH 10/11] docs/qapi-code-gen: add "Intro" subsection John Snow
2026-10-01 17:22 ` [PATCH 11/11] docs/qapi-code-gen: add "Tagged sections" cross-references John Snow
2026-10-06 11:31 ` [PATCH 00/11] docs/qapi: revise and expand QAPI documentation spec 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=87cxtndy43.fsf@pond.sub.org \
    --to=armbru@redhat.com \
    --cc=jsnow@redhat.com \
    --cc=michael.roth@amd.com \
    --cc=pierrick.bouvier@oss.qualcomm.com \
    --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.