From: Markus Armbruster <armbru@redhat.com>
To: "Dr. David Alan Gilbert" <dave@treblig.org>
Cc: "Daniel P. Berrangé" <berrange@redhat.com>,
"Michael S. Tsirkin" <mst@redhat.com>,
"Vladimir Sementsov-Ogievskiy" <vsementsov@yandex-team.ru>,
qemu-block@nongnu.org, qemu-devel@nongnu.org, eblake@redhat.com,
eduardo@habkost.net, pbonzini@redhat.com, hreitz@redhat.com,
kwolf@redhat.com, raphael.norwitz@nutanix.com,
yc-core@yandex-team.ru, den-plotnikov@yandex-team.ru,
daniil.tatianin@yandex.ru
Subject: Re: [PATCH 4/4] qapi: introduce CONFIG_READ event
Date: Thu, 19 Oct 2023 09:05:12 +0200 [thread overview]
Message-ID: <877cnjks7r.fsf@pond.sub.org> (raw)
In-Reply-To: <ZS_s0RE0ES9mvFar@gallifrey> (David Alan Gilbert's message of "Wed, 18 Oct 2023 14:33:53 +0000")
"Dr. David Alan Gilbert" <dave@treblig.org> writes:
> Using x- for events makes sense to me; the semantics of events can be
> quite subtle; often you don't find out how broken they are until you
> wire them through libvirt and up the stack; so it's not impossible
> you might need to change it - but then without the x- the semantics
> (rather than existence) of the event is carved in stone.
It is carved in stone unless feature 'unstable' is declared. The name
gets no vote.
We may elect to name unstable QAPI things 'x-FOO' to help humans.
[...]
next prev parent reply other threads:[~2023-10-19 7:06 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-06 20:20 [PATCH 0/4] vhost-user-blk: live resize additional APIs Vladimir Sementsov-Ogievskiy
2023-10-06 20:20 ` [PATCH 1/4] vhost-user-blk: simplify and fix vhost_user_blk_handle_config_change Vladimir Sementsov-Ogievskiy
2023-10-23 9:31 ` Raphael Norwitz
2023-10-06 20:20 ` [PATCH 2/4] qapi: introduce device-sync-config Vladimir Sementsov-Ogievskiy
2023-10-17 14:57 ` Markus Armbruster
2023-10-17 15:32 ` Vladimir Sementsov-Ogievskiy
2023-10-18 6:08 ` Markus Armbruster
2023-10-06 20:20 ` [PATCH 3/4] qapi: device-sync-config: check runstate Vladimir Sementsov-Ogievskiy
2023-10-06 20:20 ` [PATCH 4/4] qapi: introduce CONFIG_READ event Vladimir Sementsov-Ogievskiy
2023-10-17 15:00 ` Markus Armbruster
2023-10-17 15:44 ` Vladimir Sementsov-Ogievskiy
2023-10-18 6:47 ` Markus Armbruster
2023-10-18 8:51 ` Vladimir Sementsov-Ogievskiy
2023-10-18 10:36 ` Markus Armbruster
2023-10-18 10:51 ` Michael S. Tsirkin
2023-10-18 10:59 ` Daniel P. Berrangé
2023-10-18 12:02 ` Markus Armbruster
2023-10-18 12:07 ` Daniel P. Berrangé
2023-10-18 14:33 ` Dr. David Alan Gilbert
2023-10-19 7:05 ` Markus Armbruster [this message]
2023-10-19 7:10 ` Markus Armbruster
2023-10-18 12:39 ` Vladimir Sementsov-Ogievskiy
2023-10-19 7:01 ` 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=877cnjks7r.fsf@pond.sub.org \
--to=armbru@redhat.com \
--cc=berrange@redhat.com \
--cc=daniil.tatianin@yandex.ru \
--cc=dave@treblig.org \
--cc=den-plotnikov@yandex-team.ru \
--cc=eblake@redhat.com \
--cc=eduardo@habkost.net \
--cc=hreitz@redhat.com \
--cc=kwolf@redhat.com \
--cc=mst@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=raphael.norwitz@nutanix.com \
--cc=vsementsov@yandex-team.ru \
--cc=yc-core@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.