From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Vladimir Sementsov-Ogievskiy <vsementsov@yandex-team.ru>
Cc: armbru@redhat.com, qemu-devel@nongnu.org, eblake@redhat.com
Subject: Re: [PATCH v2 00/33] qapi: docs: width=70 and two spaces between sentences
Date: Mon, 13 Oct 2025 09:11:38 +0100 [thread overview]
Message-ID: <aOy0OtaNT9A48rhQ@redhat.com> (raw)
In-Reply-To: <20251011140441.297246-1-vsementsov@yandex-team.ru>
On Sat, Oct 11, 2025 at 05:04:06PM +0300, Vladimir Sementsov-Ogievskiy wrote:
> Hi all!
>
> Let's bring the documentation in line with the requirements. And
> do check these requirements in QAPI parser.
This implicitly assumes that the requirements are desirable.
This is a large number of patches, showing the requirements are widely
ignored today. When I look at the changes in the patches my overwhealming
reaction is that they are not beneficial, which in turn makes me believe
the requirements should be changed to match the reality of the code,
rather than the reverse.
With regards,
Daniel
--
|: https://berrange.com -o- https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org -o- https://fstop138.berrange.com :|
|: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|
next prev parent reply other threads:[~2025-10-13 8:12 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 ` Daniel P. Berrangé [this message]
2025-10-15 14:11 ` [PATCH v2 00/33] qapi: " 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
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=aOy0OtaNT9A48rhQ@redhat.com \
--to=berrange@redhat.com \
--cc=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.