All of lore.kernel.org
 help / color / mirror / Atom feed
From: Markus Armbruster <armbru@redhat.com>
To: Vladimir Sementsov-Ogievskiy <vsementsov@yandex-team.ru>
Cc: qemu-devel@nongnu.org,  eblake@redhat.com
Subject: Re: [PATCH v2 00/33] qapi: docs: width=70 and two spaces between sentences
Date: Wed, 29 Oct 2025 10:08:35 +0100	[thread overview]
Message-ID: <87sef2qdm4.fsf@pond.sub.org> (raw)
In-Reply-To: <20251011140441.297246-1-vsementsov@yandex-team.ru> (Vladimir Sementsov-Ogievskiy's message of "Sat, 11 Oct 2025 17:04:06 +0300")

Vladimir Sementsov-Ogievskiy <vsementsov@yandex-team.ru> writes:

> Hi all!
>
> Let's bring the documentation in line with the requirements. And
> do check these requirements in QAPI parser.

Prior art:

    01bed0ff14 qapi: Refill doc comments to conform to conventions
    7270819384 qga/qapi-schema: Refill doc comments to conform to current conventions
    209e64d9ed qapi: Refill doc comments to conform to current conventions

These only touched prose.

Your series also touches examples, is split per source file, and adds
code to enforce the rules automatically.

Automatic enforcement makes a ton of sense.  Should've tried to code it
up long ago.  Much appreciated!  However, it's in the first patch.  It
needs to go last to not break bisection.

I don't think splitting per source file is necessary.

I'd prefer to put aside examples for now and focus on prose, since the
case for prose is much stronger.

Since I already split off the prose changes for my own review purposes,
there's no need for you to do that again.  I'll take care of it.

However, we need to adjust the enforcement code to skip examples.

Examples are marked up with ReST directive qmp-example.  They look like
this:

    # .. qmp-example::
    #
    #     the example
    #         text is
    #     indented

The stupidest solution that could possibly work is to start skipping the
checks at

    # .. qmp-example::

and resume it at the first unindented line.

This is of course a hack: it second-guesses the ReST parser.  I think
it's good enough.

If we in a later step decide reflowing the examples is usful, the hack
goes away.

Would you be willing to take care of that part?



  parent reply	other threads:[~2025-10-29  9:09 UTC|newest]

Thread overview: 43+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-11 14:04 [PATCH v2 00/33] qapi: docs: width=70 and two spaces between sentences Vladimir Sementsov-Ogievskiy
2025-10-11 14:04 ` [PATCH v2 01/33] qapi: Add documentation format validation Vladimir Sementsov-Ogievskiy
2025-10-11 14:04 ` [PATCH v2 02/33] qapi/acpi.json: docs: width=70 and two spaces between sentences Vladimir Sementsov-Ogievskiy
2025-10-11 14:04 ` [PATCH v2 03/33] qapi/audio.json: " Vladimir Sementsov-Ogievskiy
2025-10-11 14:04 ` [PATCH v2 04/33] qapi/block-core.json: " Vladimir Sementsov-Ogievskiy
2025-10-11 14:04 ` [PATCH v2 05/33] qapi/block-export.json: " Vladimir Sementsov-Ogievskiy
2025-10-11 14:04 ` [PATCH v2 06/33] qapi/block.json: " Vladimir Sementsov-Ogievskiy
2025-10-11 14:04 ` [PATCH v2 07/33] qapi/char.json: " Vladimir Sementsov-Ogievskiy
2025-10-11 14:04 ` [PATCH v2 08/33] qapi/crypto.json: " Vladimir Sementsov-Ogievskiy
2025-10-11 14:04 ` [PATCH v2 09/33] qapi/dump.json: " Vladimir Sementsov-Ogievskiy
2025-10-11 14:04 ` [PATCH v2 10/33] qapi/introspect.json: " Vladimir Sementsov-Ogievskiy
2025-10-11 14:04 ` [PATCH v2 11/33] qapi/job.json: " Vladimir Sementsov-Ogievskiy
2025-10-11 14:04 ` [PATCH v2 12/33] qapi/machine-s390x.json: " Vladimir Sementsov-Ogievskiy
2025-10-11 14:04 ` [PATCH v2 13/33] qapi/machine.json: " Vladimir Sementsov-Ogievskiy
2025-10-11 14:04 ` [PATCH v2 14/33] qapi/migration.json: " Vladimir Sementsov-Ogievskiy
2025-10-11 14:04 ` [PATCH v2 15/33] qapi/misc-arm.json: " Vladimir Sementsov-Ogievskiy
2025-10-11 14:04 ` [PATCH v2 16/33] qapi/misc-i386.json: " Vladimir Sementsov-Ogievskiy
2025-10-11 14:04 ` [PATCH v2 17/33] qapi/misc.json: " Vladimir Sementsov-Ogievskiy
2025-10-11 14:04 ` [PATCH v2 18/33] qapi/net.json: " Vladimir Sementsov-Ogievskiy
2025-10-11 14:04 ` [PATCH v2 19/33] qapi/qdev.json: " Vladimir Sementsov-Ogievskiy
2025-10-11 14:04 ` [PATCH v2 20/33] qapi/qom.json: " Vladimir Sementsov-Ogievskiy
2025-10-11 14:04 ` [PATCH v2 21/33] qapi/replay.json: " Vladimir Sementsov-Ogievskiy
2025-10-11 14:04 ` [PATCH v2 22/33] qapi/rocker.json: " Vladimir Sementsov-Ogievskiy
2025-10-11 14:04 ` [PATCH v2 23/33] qapi/run-state.json: " Vladimir Sementsov-Ogievskiy
2025-10-11 14:04 ` [PATCH v2 24/33] qapi/sockets.json: " Vladimir Sementsov-Ogievskiy
2025-10-11 14:04 ` [PATCH v2 25/33] qapi/stats.json: " Vladimir Sementsov-Ogievskiy
2025-10-11 14:04 ` [PATCH v2 26/33] qapi/tpm.json: " Vladimir Sementsov-Ogievskiy
2025-10-11 14:04 ` [PATCH v2 27/33] qapi/trace.json: " Vladimir Sementsov-Ogievskiy
2025-10-14 18:22   ` Stefan Hajnoczi
2025-10-11 14:04 ` [PATCH v2 28/33] qapi/transaction.json: " Vladimir Sementsov-Ogievskiy
2025-10-11 14:04 ` [PATCH v2 29/33] qapi/ui.json: " Vladimir Sementsov-Ogievskiy
2025-10-11 14:04 ` [PATCH v2 30/33] qapi/vfio.json: " Vladimir Sementsov-Ogievskiy
2025-10-11 14:04 ` [PATCH v2 31/33] qapi/virtio.json: " Vladimir Sementsov-Ogievskiy
2025-10-11 14:04 ` [PATCH v2 32/33] qga/qapi-schema.json: " Vladimir Sementsov-Ogievskiy
2025-10-11 14:04 ` [PATCH v2 33/33] qapi/acpi-hest.json: " Vladimir Sementsov-Ogievskiy
2025-10-13  8:11 ` [PATCH v2 00/33] qapi: " Daniel P. Berrangé
2025-10-15 14:11   ` Vladimir Sementsov-Ogievskiy
2025-10-29  8:29   ` Markus Armbruster
2025-10-29  9:28     ` Vladimir Sementsov-Ogievskiy
2025-10-29 10:25       ` Markus Armbruster
2025-10-29  9:08 ` Markus Armbruster [this message]
2025-10-29  9:24   ` Vladimir Sementsov-Ogievskiy
2025-10-29 10:31     ` 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=87sef2qdm4.fsf@pond.sub.org \
    --to=armbru@redhat.com \
    --cc=eblake@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=vsementsov@yandex-team.ru \
    /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.