From: Peter Maydell <peter.maydell@linaro.org>
To: Eduardo Habkost <ehabkost@redhat.com>
Cc: QEMU Developers <qemu-devel@nongnu.org>, Cleber Rosa <crosa@redhat.com>
Subject: Re: [Qemu-devel] [PULL 0/2] Python queue, 2019-08-28
Date: Tue, 3 Sep 2019 16:48:18 +0100 [thread overview]
Message-ID: <CAFEAcA_=bDSbSqo17HvrD3pv+126695W+LfyXMfGXNCGemffAA@mail.gmail.com> (raw)
In-Reply-To: <20190828192340.14025-1-ehabkost@redhat.com>
On Wed, 28 Aug 2019 at 20:23, Eduardo Habkost <ehabkost@redhat.com> wrote:
>
> The following changes since commit 23919ddfd56135cad3cb468a8f54d5a595f024f4:
>
> Merge remote-tracking branch 'remotes/aperard/tags/pull-xen-20190827' into staging (2019-08-27 15:52:36 +0100)
>
> are available in the Git repository at:
>
> git://github.com/ehabkost/qemu.git tags/python-next-pull-request
>
> for you to fetch changes up to 406ab2f331555cfcf320fe2a77949d7f8af7ab32:
>
> configure: more resilient Python version capture (2019-08-27 16:57:24 -0300)
>
> ----------------------------------------------------------------
> Python queue, 2019-08-28
>
> Bug fix:
> * configure: more resilient Python version capture (Cleber Rosa)
>
> Cleanup:
> * BootLinuxSshTest: Only use 'test' for unittest.TestCase method
> names (Philippe Mathieu-Daudé)
Applied, thanks.
Please update the changelog at https://wiki.qemu.org/ChangeLog/4.2
for any user-visible changes.
-- PMM
prev parent reply other threads:[~2019-09-03 16:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-28 19:23 [Qemu-devel] [PULL 0/2] Python queue, 2019-08-28 Eduardo Habkost
2019-08-28 19:23 ` [Qemu-devel] [PULL 1/2] BootLinuxSshTest: Only use 'test' for unittest.TestCase method names Eduardo Habkost
2019-08-28 19:23 ` [Qemu-devel] [PULL 2/2] configure: more resilient Python version capture Eduardo Habkost
2019-09-03 15:48 ` 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_=bDSbSqo17HvrD3pv+126695W+LfyXMfGXNCGemffAA@mail.gmail.com' \
--to=peter.maydell@linaro.org \
--cc=crosa@redhat.com \
--cc=ehabkost@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).