From: "Philippe Mathieu-Daudé" <philmd@linaro.org>
To: John Snow <jsnow@redhat.com>, Markus Armbruster <armbru@redhat.com>
Cc: qemu-devel <qemu-devel@nongnu.org>
Subject: Re: Sample 'qapi-schema-diff' output for v9.0.0 vs origin/master
Date: Thu, 13 Jun 2024 10:49:59 +0200 [thread overview]
Message-ID: <c826b3dc-2a49-493f-8e6d-efffbfc74f70@linaro.org> (raw)
In-Reply-To: <CAFn=p-a4MOZGDd7nj_gEf0fT7nvwa40pLJ1GiGOTj3uNhSq1tg@mail.gmail.com>
Hi John,
On 12/6/24 20:40, John Snow wrote:
> Hiya, here's some draft output of a script I'm working on to summarize
> QMP wire format differences between QEMU versions.
>
> This script works in terms of the QMP *wire format*, not the QAPI
> *specification*. As a consequence, *almost* all type names are stripped
> from this output and all nested structures are fully inlined - so
> changes to shared data structures, enums, etc will manifest as many
> independent changes. Similarly, changes to type names and type
> factorings that do not change the wire format will not appear in this
> report at all.
Do you include changes on unstable features or are you skipping them?
Possible feature request: skip them by default until a --unstable
CLI option is used.
>
> This is still a WIP: if conditionals and features may not be fully
> represented in this summary report.
Regards,
Phil.
next prev parent reply other threads:[~2024-06-13 8:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-12 18:40 Sample 'qapi-schema-diff' output for v9.0.0 vs origin/master John Snow
2024-06-13 8:49 ` Philippe Mathieu-Daudé [this message]
2024-06-13 14:07 ` John Snow
2024-06-13 14:54 ` Daniel P. Berrangé
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=c826b3dc-2a49-493f-8e6d-efffbfc74f70@linaro.org \
--to=philmd@linaro.org \
--cc=armbru@redhat.com \
--cc=jsnow@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).