qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Peter Maydell <peter.maydell@linaro.org>
To: Markus Armbruster <armbru@redhat.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [PULL 00/18] QAPI patches patches for 2024-03-04
Date: Tue, 5 Mar 2024 13:45:14 +0000	[thread overview]
Message-ID: <CAFEAcA-u9E5_rmYti5NMQVZvh4qh_tW140gqPESQ9d+w_VYdjg@mail.gmail.com> (raw)
In-Reply-To: <20240304063236.213955-1-armbru@redhat.com>

On Mon, 4 Mar 2024 at 06:32, Markus Armbruster <armbru@redhat.com> wrote:
>
> The following changes since commit e1007b6bab5cf97705bf4f2aaec1f607787355b8:
>
>   Merge tag 'pull-request-2024-03-01' of https://gitlab.com/thuth/qemu into staging (2024-03-01 10:14:32 +0000)
>
> are available in the Git repository at:
>
>   https://repo.or.cz/qemu/armbru.git tags/pull-qapi-2024-03-04
>
> for you to fetch changes up to 018d5fb1f91c7f316b4b8501a78e7219bb9fb614:
>
>   migration: simplify exec migration functions (2024-03-04 07:12:40 +0100)
>
> ----------------------------------------------------------------
> QAPI patches patches for 2024-03-04
>
> ----------------------------------------------------------------


Applied, thanks.

Please update the changelog at https://wiki.qemu.org/ChangeLog/9.0
for any user-visible changes.

-- PMM


      parent reply	other threads:[~2024-03-05 13:47 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-04  6:32 [PULL 00/18] QAPI patches patches for 2024-03-04 Markus Armbruster
2024-03-04  6:32 ` [PULL 01/18] qapi: Memorize since & returns sections Markus Armbruster
2024-03-04  6:32 ` [PULL 02/18] qapi: Slightly clearer error message for invalid "Returns" section Markus Armbruster
2024-03-04  6:32 ` [PULL 03/18] qapi: New documentation section tag "Errors" Markus Armbruster
2024-03-04  6:32 ` [PULL 04/18] qapi: Move error documentation to new "Errors" sections Markus Armbruster
2024-03-04  6:32 ` [PULL 05/18] qapi: Delete useless "Returns" sections Markus Armbruster
2024-03-04  6:32 ` [PULL 06/18] qapi: Clean up " Markus Armbruster
2024-03-04  6:32 ` [PULL 07/18] qapi/yank: Tweak @yank's error description for consistency Markus Armbruster
2024-03-04  6:32 ` [PULL 08/18] qga/qapi-schema: Move error documentation to new "Errors" sections Markus Armbruster
2024-03-04  6:32 ` [PULL 09/18] qga/qapi-schema: Delete useless "Returns" sections Markus Armbruster
2024-03-04  6:32 ` [PULL 10/18] qga/qapi-schema: Clean up " Markus Armbruster
2024-03-04  6:32 ` [PULL 11/18] qga/qapi-schema: Tweak documentation of fsfreeze commands Markus Armbruster
2024-03-04  6:32 ` [PULL 12/18] qga/qapi-schema: Fix guest-set-memory-blocks documentation Markus Armbruster
2024-03-04  6:32 ` [PULL 13/18] qapi: Reject "Returns" section when command doesn't return anything Markus Armbruster
2024-03-04  6:32 ` [PULL 14/18] docs/devel/writing-monitor-commands: Repair a decade of rot Markus Armbruster
2024-03-04  6:32 ` [PULL 15/18] docs/devel/writing-monitor-commands: Minor improvements Markus Armbruster
2024-03-04  6:32 ` [PULL 16/18] qapi: New QAPI_LIST_LENGTH() Markus Armbruster
2024-03-04  6:32 ` [PULL 17/18] qapi: New strv_from_str_list() Markus Armbruster
2024-03-04  6:32 ` [PULL 18/18] migration: simplify exec migration functions Markus Armbruster
2024-03-05 13:45 ` Peter Maydell [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=CAFEAcA-u9E5_rmYti5NMQVZvh4qh_tW140gqPESQ9d+w_VYdjg@mail.gmail.com \
    --to=peter.maydell@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).