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 03/11] docs/qapi-code-gen: add "TODO" subsection
Date: Tue, 06 Oct 2026 10:02:57 +0200	[thread overview]
Message-ID: <87ik3fdzny.fsf@pond.sub.org> (raw)
In-Reply-To: <20261001172239.2825745-4-jsnow@redhat.com> (John Snow's message of "Thu, 1 Oct 2026 13:22:30 -0400")

John Snow <jsnow@redhat.com> writes:

> Split the "TODO" section description into its own little section, and
> add a dedicated example for it.
>
> Signed-off-by: John Snow <jsnow@redhat.com>
> ---
>  docs/devel/qapi-code-gen.rst | 14 ++++++++++++--
>  1 file changed, 12 insertions(+), 2 deletions(-)
>
> diff --git a/docs/devel/qapi-code-gen.rst b/docs/devel/qapi-code-gen.rst
> index 0f66f012be1..977ed1aa3bd 100644
> --- a/docs/devel/qapi-code-gen.rst
> +++ b/docs/devel/qapi-code-gen.rst
> @@ -1037,8 +1037,7 @@ detailing a relevant error condition.  For example::
>  A "Since: x.y" tagged section lists the release that introduced the
>  definition.
>  
> -"TODO" sections are not rendered (they are for developers, not users of
> -QMP).  In other sections, the text is formatted, and rST markup can be
> +In other sections, the text is formatted, and rST markup can be
>  used.
>  
>  QMP Examples can be added by using the ``.. qmp-example::`` directive.
> @@ -1089,6 +1088,17 @@ Highlighting in non-QMP languages can be accomplished by using the
>  achieved by omitting the language argument.
>  
>  
> +TODO
> +^^^^
> +
> +"TODO" tagged sections are not rendered (they are for developers, not users of

Wrap lines at colum 70, please.

> +QMP). They can appear anywhere after the introductory section::

Two spaces between sentences for consistency, please.

> +
> +  #
> +  ## TODO: This is not rendered in the documentation.

Why the second '#'?

> +  #
> +
> +
>  Putting it all together
>  ^^^^^^^^^^^^^^^^^^^^^^^



  reply	other threads:[~2026-10-07  8:19 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 [this message]
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
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=87ik3fdzny.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.