From: Peter Maydell <peter.maydell@linaro.org>
To: Eric Blake <eblake@redhat.com>
Cc: QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PULL 0/4] QAPI patches for 2018-03-23, for 2.12-rc1
Date: Sat, 24 Mar 2018 16:33:49 +0000 [thread overview]
Message-ID: <CAFEAcA8JzkBBpXTMa2RtXu4PesEBMPOfrbyRZCbTmPDK8zVrYw@mail.gmail.com> (raw)
In-Reply-To: <20180323173741.1445744-1-eblake@redhat.com>
On 23 March 2018 at 17:37, Eric Blake <eblake@redhat.com> wrote:
> The following changes since commit 4c2c1015905fa1d616750dfe024b4c0b35875950:
>
> Merge remote-tracking branch 'remotes/borntraeger/tags/s390x-20180323' into staging (2018-03-23 10:20:54 +0000)
>
> are available in the Git repository at:
>
> git://repo.or.cz/qemu/ericb.git tags/pull-qapi-2018-03-23
>
> for you to fetch changes up to 39615354fc07af34e04ab5efb5b6d478b0d24e32:
>
> qapi: Force UTF8 encoding when parsing qapi files (2018-03-23 12:29:07 -0500)
>
> There may be another rc1 pull request on Monday, but let's get
> these in sooner rather than later to minimize the window where
> iotests are broken during bisects.
>
> ----------------------------------------------------------------
> qapi patches for 2018-03-12, 2.12-rc1
>
> - Peter Xu: 0/4 Turn OOB off for 2.12-rc1, revert OOB tests
> - Eric Blake: qapi: Force UTF8 encoding when parsing qapi files
>
Applied, thanks.
-- PMM
prev parent reply other threads:[~2018-03-24 16:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-23 17:37 [Qemu-devel] [PULL 0/4] QAPI patches for 2018-03-23, for 2.12-rc1 Eric Blake
2018-03-23 17:37 ` [Qemu-devel] [PULL 1/4] Revert "tests: qmp-test: add oob test" Eric Blake
2018-03-23 17:37 ` [Qemu-devel] [PULL 2/4] Revert "tests: qmp-test: verify command batching" Eric Blake
2018-03-23 17:37 ` [Qemu-devel] [PULL 3/4] Revert "monitor: enable IO thread for (qmp & !mux) typed" Eric Blake
2018-03-23 17:37 ` [Qemu-devel] [PULL 4/4] qapi: Force UTF8 encoding when parsing qapi files Eric Blake
2018-03-24 16:33 ` 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=CAFEAcA8JzkBBpXTMa2RtXu4PesEBMPOfrbyRZCbTmPDK8zVrYw@mail.gmail.com \
--to=peter.maydell@linaro.org \
--cc=eblake@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).