qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Peter Maydell <peter.maydell@linaro.org>
To: Eduardo Habkost <ehabkost@redhat.com>
Cc: "Fam Zheng" <fam@euphon.net>,
	"Aleksandar Rikalo" <arikalo@wavecomp.com>,
	"Alex Bennée" <alex.bennee@linaro.org>,
	"QEMU Developers" <qemu-devel@nongnu.org>,
	"Aleksandar Markovic" <amarkovic@wavecomp.com>,
	"Cleber Rosa" <crosa@redhat.com>,
	"Philippe Mathieu-Daudé" <philmd@redhat.com>,
	"Aurelien Jarno" <aurelien@aurel32.net>
Subject: Re: [Qemu-devel] [PULL 0/6] Python queue, 2019-06-11
Date: Wed, 12 Jun 2019 13:49:27 +0100	[thread overview]
Message-ID: <CAFEAcA-HK=1EyCT7w+it1Gq9WTOpq=4m2kHbM2upPvWcOAoGew@mail.gmail.com> (raw)
In-Reply-To: <20190611171456.23444-1-ehabkost@redhat.com>

On Tue, 11 Jun 2019 at 18:15, Eduardo Habkost <ehabkost@redhat.com> wrote:
>
> Changes from 2019-06-07: Python 2 deprecation and Python 3 check
> for 3.5+ were removed.
>
> The following changes since commit 219dca61ebf41625831d4f96a720852baf44b762:
>
>   Merge remote-tracking branch 'remotes/ehabkost/tags/x86-next-pull-request' into staging (2019-06-11 16:02:07 +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 6d7a134da4afebe8551a69329478415cfb4cbe91:
>
>   travis: Make check-acceptance job more verbose (2019-06-11 14:13:09 -0300)
>
> ----------------------------------------------------------------
> Python queue, 2019-06-11
>
> * New boot_linux_console test cases (Philippe Mathieu-Daudé)
> * Make check-acceptance Travis job more verbose (Eduardo Habkost)
>
> ----------------------------------------------------------------


Applied, thanks.

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

-- PMM


  parent reply	other threads:[~2019-06-12 13:08 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-11 17:14 [Qemu-devel] [PULL 0/6] Python queue, 2019-06-11 Eduardo Habkost
2019-06-11 17:14 ` [Qemu-devel] [PULL 1/6] tests/boot_linux_console: Let extract_from_deb handle various compressions Eduardo Habkost
2019-06-11 17:14 ` [Qemu-devel] [PULL 2/6] BootLinuxConsoleTest: Do not log empty lines Eduardo Habkost
2019-06-11 17:14 ` [Qemu-devel] [PULL 3/6] BootLinuxConsoleTest: Test the SmartFusion2 board Eduardo Habkost
2019-06-11 17:14 ` [Qemu-devel] [PULL 4/6] BootLinuxConsoleTest: Test nanoMIPS kernels on the I7200 CPU Eduardo Habkost
2019-06-11 17:14 ` [Qemu-devel] [PULL 5/6] BootLinuxConsoleTest: Run kerneltests BusyBox on Malta Eduardo Habkost
2019-06-11 17:14 ` [Qemu-devel] [PULL 6/6] travis: Make check-acceptance job more verbose Eduardo Habkost
2019-06-12 20:49   ` Philippe Mathieu-Daudé
2019-06-12 20:52     ` Eduardo Habkost
2019-06-12 22:33       ` Philippe Mathieu-Daudé
2019-06-12 22:47     ` Cleber Rosa
2019-06-12 23:12       ` Philippe Mathieu-Daudé
2019-06-12 12:49 ` Peter Maydell [this message]
2019-06-18 13:27 ` [Qemu-devel] [PULL 0/6] Python queue, 2019-06-11 Peter Maydell
2019-06-18 14:01   ` Cleber Rosa
2019-06-18 15:38     ` Cleber Rosa

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-HK=1EyCT7w+it1Gq9WTOpq=4m2kHbM2upPvWcOAoGew@mail.gmail.com' \
    --to=peter.maydell@linaro.org \
    --cc=alex.bennee@linaro.org \
    --cc=amarkovic@wavecomp.com \
    --cc=arikalo@wavecomp.com \
    --cc=aurelien@aurel32.net \
    --cc=crosa@redhat.com \
    --cc=ehabkost@redhat.com \
    --cc=fam@euphon.net \
    --cc=philmd@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).