From: Markus Armbruster <armbru@redhat.com>
To: John Snow <jsnow@redhat.com>
Cc: qemu-devel <qemu-devel@nongnu.org>,
"Michael Roth" <michael.roth@amd.com>,
"Eric Blake" <eblake@redhat.com>,
"Marc-André Lureau" <marcandre.lureau@redhat.com>
Subject: Re: [PATCH 0/2] docs/devel/qapi-code-gen: Update features doc, minor improvements
Date: Wed, 15 Feb 2023 13:07:58 +0100 [thread overview]
Message-ID: <87ilg3b081.fsf@pond.sub.org> (raw)
In-Reply-To: <CAFn=p-Yvv4Bcsu0158+3caJ2maxGb-0ZUCTfu1uLnve9-swGrg@mail.gmail.com> (John Snow's message of "Tue, 14 Feb 2023 11:51:34 -0500")
John Snow <jsnow@redhat.com> writes:
> On Tue, Feb 14, 2023, 11:49 AM John Snow <jsnow@redhat.com> wrote:
>
>>
>>
>> On Mon, Feb 13, 2023, 8:20 AM Markus Armbruster <armbru@redhat.com> wrote:
>>
>>> *** BLURB HERE ***
>>>
>>
>> 🤫
Uh, thank you for following my written instructions literally, and...
>>> Markus Armbruster (2):
>>> docs/devel/qapi-code-gen: Belatedly update features documentation
>>> docs/devel/qapi-code-gen: Fix a missing 'may', clarify SchemaInfo
>>>
>>> docs/devel/qapi-code-gen.rst | 16 ++++++++--------
>>> 1 file changed, 8 insertions(+), 8 deletions(-)
>>>
>>> --
>>> 2.39.0
>>>
>>
> Oops, also meant to add:
>
> Reviewed-by: John Snow <jsnow@redhat.com>
... thank you for reviewing!
prev parent reply other threads:[~2023-02-15 12:08 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-13 13:20 [PATCH 0/2] docs/devel/qapi-code-gen: Update features doc, minor improvements Markus Armbruster
2023-02-13 13:20 ` [PATCH 1/2] docs/devel/qapi-code-gen: Belatedly update features documentation Markus Armbruster
2023-02-13 15:05 ` Eric Blake
2023-02-13 13:20 ` [PATCH 2/2] docs/devel/qapi-code-gen: Fix a missing 'may', clarify SchemaInfo Markus Armbruster
2023-02-13 15:07 ` Eric Blake
2023-02-14 16:49 ` [PATCH 0/2] docs/devel/qapi-code-gen: Update features doc, minor improvements John Snow
2023-02-14 16:51 ` John Snow
2023-02-15 12:07 ` Markus Armbruster [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=87ilg3b081.fsf@pond.sub.org \
--to=armbru@redhat.com \
--cc=eblake@redhat.com \
--cc=jsnow@redhat.com \
--cc=marcandre.lureau@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.