From: Markus Armbruster <armbru@redhat.com>
To: John Snow <jsnow@redhat.com>
Cc: qemu-devel@nongnu.org, Michael Roth <michael.roth@amd.com>
Subject: Re: [PATCH v4 0/6] qapi: static typing conversion, pt5c
Date: Tue, 21 Feb 2023 07:42:47 +0100 [thread overview]
Message-ID: <87sfezzfh4.fsf@pond.sub.org> (raw)
In-Reply-To: <CAFn=p-ZAnqRr7SYVO8n_DaFDUavFykNYwaQy4fCWubTx686kJg@mail.gmail.com> (John Snow's message of "Mon, 20 Feb 2023 20:26:21 -0500")
John Snow <jsnow@redhat.com> writes:
> On Wed, Feb 15, 2023 at 8:39 AM Markus Armbruster <armbru@redhat.com> wrote:
>>
>> I had a few suggestions, but none of them requires a respin. Let's
>> discuss them, and then I merge.
>
> Hiya, I lost track of things a little due to the other Python
> discussion. Who is waiting for whom?
Just two questions remain:
* PATCH 3: Dumb down check_keys() argument all the way to List[str]?
* PATCH 4: Suggested commit message addition okay?
We settle them, and then I'll take it from there.
next prev parent reply other threads:[~2023-02-21 6:43 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-15 0:00 [PATCH v4 0/6] qapi: static typing conversion, pt5c John Snow
2023-02-15 0:00 ` [PATCH v4 1/6] qapi: Update flake8 config John Snow
2023-02-15 0:00 ` [PATCH v4 2/6] qapi: update pylint configuration John Snow
2023-02-15 0:00 ` [PATCH v4 3/6] qapi: Add minor typing workaround for 3.6 John Snow
2023-02-15 7:15 ` Markus Armbruster
2023-02-15 13:36 ` Markus Armbruster
2023-02-15 14:46 ` John Snow
2023-02-15 0:00 ` [PATCH v4 4/6] qapi/parser: add QAPIExpression type John Snow
2023-02-15 9:43 ` Markus Armbruster
2023-02-15 19:05 ` John Snow
2023-02-15 0:00 ` [PATCH v4 5/6] qapi: remove _JSONObject John Snow
2023-02-15 9:44 ` Markus Armbruster
2023-02-15 0:00 ` [PATCH v4 6/6] qapi: remove JSON value FIXME John Snow
2023-02-15 11:13 ` Markus Armbruster
2023-02-15 13:39 ` [PATCH v4 0/6] qapi: static typing conversion, pt5c Markus Armbruster
2023-02-21 1:26 ` John Snow
2023-02-21 6:42 ` Markus Armbruster [this message]
2023-02-21 17:32 ` John Snow
2023-02-22 9:16 ` 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=87sfezzfh4.fsf@pond.sub.org \
--to=armbru@redhat.com \
--cc=jsnow@redhat.com \
--cc=michael.roth@amd.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 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.