From: Markus Armbruster <armbru@redhat.com>
To: "Philippe Mathieu-Daudé" <philmd@linaro.org>
Cc: qemu-devel@nongnu.org, eblake@redhat.com
Subject: Re: [PATCH] qapi: Belatedly update CompatPolicy documentation for unstable
Date: Mon, 09 Oct 2023 13:46:22 +0200 [thread overview]
Message-ID: <875y3g10j5.fsf@pond.sub.org> (raw)
In-Reply-To: <78921033-d8f5-d736-0437-b805e78c1a55@linaro.org> ("Philippe Mathieu-Daudé"'s message of "Mon, 9 Oct 2023 13:19:06 +0200")
Philippe Mathieu-Daudé <philmd@linaro.org> writes:
> On 9/10/23 13:04, Markus Armbruster wrote:
>> Commit 57df0dff1a1 (qapi: Extend -compat to set policy for unstable
>> interfaces) neglected to update the "Limitation" paragraph to mention
>
> With retrospective, 'experimental' seems more meaningful. Anyway,
> too late.
Experiments are a major use for interfaces without stability promise,
but there's also debugging aids and such.
>> feature 'unstable' in addition to feature 'deprecated'. Do that now.
>> Signed-off-by: Markus Armbruster <armbru@redhat.com>
>> ---
>> qapi/compat.json | 4 ++--
>> 1 file changed, 2 insertions(+), 2 deletions(-)
>> diff --git a/qapi/compat.json b/qapi/compat.json
>> index f4c19837eb..42034d9368 100644
>> --- a/qapi/compat.json
>> +++ b/qapi/compat.json
>> @@ -43,8 +43,8 @@
>> # This is intended for testing users of the management interfaces.
>> #
>> # Limitation: covers only syntactic aspects of QMP, i.e. stuff tagged
>> -# with feature 'deprecated'. We may want to extend it to cover
>> -# semantic aspects and CLI.
>> +# with feature 'deprecated' or 'unstable'. We may want to extend it
>> +# to cover semantic aspects and CLI.
>
> Reviewed-by: Philippe Mathieu-Daudé <philmd@linaro.org>
Thanks!
next prev parent reply other threads:[~2023-10-09 11:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-09 11:04 [PATCH] qapi: Belatedly update CompatPolicy documentation for unstable Markus Armbruster
2023-10-09 11:19 ` Philippe Mathieu-Daudé
2023-10-09 11:46 ` Markus Armbruster [this message]
2023-10-16 10:52 ` 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=875y3g10j5.fsf@pond.sub.org \
--to=armbru@redhat.com \
--cc=eblake@redhat.com \
--cc=philmd@linaro.org \
--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.