From: Eric Blake <eblake@redhat.com>
To: Markus Armbruster <armbru@redhat.com>
Cc: qemu-devel@nongnu.org, michael.roth@amd.com, jsnow@redhat.com,
marcandre.lureau@redhat.com
Subject: Re: [PATCH 1/2] docs/devel/qapi-code-gen: Belatedly update features documentation
Date: Mon, 13 Feb 2023 09:05:53 -0600 [thread overview]
Message-ID: <20230213150553.ronttibejqp532fr@redhat.com> (raw)
In-Reply-To: <20230213132009.918801-2-armbru@redhat.com>
On Mon, Feb 13, 2023 at 02:20:08PM +0100, Markus Armbruster wrote:
> Commit 013b4efc9be "qapi: Add feature flags to remaining
> definitions" (v5.0.0), commit 84ab0086879 "qapi: Add feature flags to
> struct members" (v5.0.0), and commit b6c18755e41 "qapi: Add feature
> flags to enum members" (v6.2.0) neglected to update section
> "Features". Make up for that.
>
> Signed-off-by: Markus Armbruster <armbru@redhat.com>
> ---
> docs/devel/qapi-code-gen.rst | 7 ++++---
> 1 file changed, 4 insertions(+), 3 deletions(-)
Reviewed-by: Eric Blake <eblake@redhat.com>
--
Eric Blake, Principal Software Engineer
Red Hat, Inc. +1-919-301-3266
Virtualization: qemu.org | libvirt.org
next prev parent reply other threads:[~2023-02-13 15:06 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 [this message]
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
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=20230213150553.ronttibejqp532fr@redhat.com \
--to=eblake@redhat.com \
--cc=armbru@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 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).