From: Zhao Liu <zhao1.liu@intel.com>
To: Eric Blake <eblake@redhat.com>, Markus Armbruster <armbru@redhat.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [PATCH 0/2] qapi/qapi-schema: Clarify the dependency relationship
Date: Thu, 30 May 2024 22:11:26 +0800 [thread overview]
Message-ID: <ZliJDp4TwCAWO+jH@intel.com> (raw)
In-Reply-To: <20240517062748.782366-1-zhao1.liu@intel.com>
Hi Eric and Markus,
Just a gentle poke. What do you think of this ordering?
Thanks,
Zhao
On Fri, May 17, 2024 at 02:27:46PM +0800, Zhao Liu wrote:
> Date: Fri, 17 May 2024 14:27:46 +0800
> From: Zhao Liu <zhao1.liu@intel.com>
> Subject: [PATCH 0/2] qapi/qapi-schema: Clarify the dependency relationship
> X-Mailer: git-send-email 2.34.1
>
> Hi,
>
> At present, the correctness of the dependencies of JSON files is ensured
> by the order in which they are listed, but in general, the mixing of
> multiple files and the lack of clear guidelines for ordering them is not
> friendly to extending and maintaining.
>
> Therefore, I have a proposal to manually categorize and sort JSON files
> generation order by dependencies/dependency hierarchy, to improve the
> readability and maintainability of qapi-schema.json.
>
> Welcome your feedback!
>
> Thanks and Best Regards,
> Zhao
> ---
> Zhao Liu (2):
> qapi: Reorder and categorize json files in qapi-schema.json
> qapi: List block-core.json in qapi-schema.json
>
> qapi/qapi-schema.json | 100 +++++++++++++++++++++++++++++-------------
> 1 file changed, 69 insertions(+), 31 deletions(-)
>
> --
> 2.34.1
>
prev parent reply other threads:[~2024-05-30 13:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-17 6:27 [PATCH 0/2] qapi/qapi-schema: Clarify the dependency relationship Zhao Liu
2024-05-17 6:27 ` [PATCH 1/2] qapi: Reorder and categorize json files in qapi-schema.json Zhao Liu
2024-05-17 6:27 ` [PATCH 2/2] qapi: List block-core.json " Zhao Liu
2024-05-30 14:11 ` Zhao Liu [this message]
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=ZliJDp4TwCAWO+jH@intel.com \
--to=zhao1.liu@intel.com \
--cc=armbru@redhat.com \
--cc=eblake@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).