From: Richard Henderson <richard.henderson@linaro.org>
To: Markus Armbruster <armbru@redhat.com>, qemu-devel@nongnu.org
Subject: Re: [PULL 0/3] QAPI patches patches for 2023-08-02
Date: Wed, 2 Aug 2023 08:14:52 -0700 [thread overview]
Message-ID: <04862d4b-d998-e557-d740-3ae863eb97c3@linaro.org> (raw)
In-Reply-To: <20230802074041.418954-1-armbru@redhat.com>
On 8/2/23 00:40, Markus Armbruster wrote:
> The following changes since commit 38a6de80b917b2a822cff0e38d83563ab401c890:
>
> Merge tag 'pull-xen-20230801' ofhttps://xenbits.xen.org/git-http/people/aperard/qemu-dm into staging (2023-08-01 07:27:31 -0700)
>
> are available in the Git repository at:
>
> https://repo.or.cz/qemu/armbru.git tags/pull-qapi-2023-08-02
>
> for you to fetch changes up to 2b3edd95186dc505f21d823119cdd0dfb23b3ee0:
>
> MAINTAINERS: Add section "Migration dirty limit and dirty page rate" (2023-08-02 09:33:38 +0200)
>
> ----------------------------------------------------------------
> QAPI patches patches for 2023-08-02
>
> ----------------------------------------------------------------
> The patches affect only documentation. Generated code does not change.
Applied, thanks. Please update https://wiki.qemu.org/ChangeLog/8.1 as appropriate.
r~
prev parent reply other threads:[~2023-08-02 15:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-02 7:40 [PULL 0/3] QAPI patches patches for 2023-08-02 Markus Armbruster
2023-08-02 7:40 ` [PULL 1/3] qapi: Reformat the dirty-limit migration doc comments Markus Armbruster
2023-08-02 7:40 ` [PULL 2/3] qapi: Craft the dirty-limit capability comment Markus Armbruster
2023-08-02 7:40 ` [PULL 3/3] MAINTAINERS: Add section "Migration dirty limit and dirty page rate" Markus Armbruster
2023-08-02 15:14 ` Richard Henderson [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=04862d4b-d998-e557-d740-3ae863eb97c3@linaro.org \
--to=richard.henderson@linaro.org \
--cc=armbru@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).