qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Peter Maydell <peter.maydell@linaro.org>
To: "Alex Bennée" <alex.bennee@linaro.org>
Cc: QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [PULL 00/14] testing updates (python, plugins)
Date: Fri, 2 Oct 2020 14:29:36 +0100	[thread overview]
Message-ID: <CAFEAcA9DApaAdK21stVPab_8jYAUeHiR4AkVDzpnaTdx5xAuvQ@mail.gmail.com> (raw)
In-Reply-To: <20201002113645.17693-1-alex.bennee@linaro.org>

On Fri, 2 Oct 2020 at 12:36, Alex Bennée <alex.bennee@linaro.org> wrote:
>
> The following changes since commit b5ce42f5d138d7546f9faa2decbd6ee8702243a3:
>
>   Merge remote-tracking branch 'remotes/jsnow-gitlab/tags/ide-pull-request' into staging (2020-10-01 19:55:10 +0100)
>
> are available in the Git repository at:
>
>   https://github.com/stsquad/qemu.git tags/pull-testing-and-python-021020-1
>
> for you to fetch changes up to 2614670b7585ce4ec503546bc3023844d392f270:
>
>   gitlab: split deprecated job into build/check stages (2020-10-02 12:31:34 +0100)
>
> ----------------------------------------------------------------
> Python testing updates:
>
>   - drop python 3.5 test from travis
>   - replace Debian 9 containers with 10
>   - increase cross build timeout
>   - bump minimum python version in configure
>   - move user plugins tests to gitlab
>   - split deprecated builds into build and test


Applied, thanks.

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

-- PMM


      parent reply	other threads:[~2020-10-02 13:30 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-02 11:36 [PULL 00/14] testing updates (python, plugins) Alex Bennée
2020-10-02 11:36 ` [PULL 01/14] migration: Silence compiler warning in global_state_store_running() Alex Bennée
2020-10-02 11:36 ` [PULL 02/14] travis.yml: Drop the default softmmu builds Alex Bennée
2020-10-02 11:36 ` [PULL 03/14] travis.yml: Update Travis to use Bionic and Focal instead of Xenial Alex Bennée
2020-10-02 11:36 ` [PULL 04/14] travis.yml: Drop the superfluous Python 3.6 build Alex Bennée
2020-10-02 11:36 ` [PULL 05/14] travis.yml: Drop the Python 3.5 build Alex Bennée
2020-10-02 11:36 ` [PULL 06/14] tests/docker: Use Fedora containers for MinGW cross-builds in the gitlab-CI Alex Bennée
2020-10-02 11:36 ` [PULL 07/14] gitlab-ci: Remove the Debian9-based containers and containers-layer3 Alex Bennée
2020-10-02 11:36 ` [PULL 08/14] tests/docker: Update the tricore container to debian 10 Alex Bennée
2020-10-02 11:36 ` [PULL 09/14] shippable.yml: Remove the Debian9-based MinGW cross-compiler tests Alex Bennée
2020-10-02 11:36 ` [PULL 10/14] tests/docker: Remove old Debian 9 containers Alex Bennée
2023-06-23 22:29   ` Philippe Mathieu-Daudé
2023-06-24 14:17     ` Philippe Mathieu-Daudé
2020-10-02 11:36 ` [PULL 11/14] gitlab-ci: Increase the timeout for the cross-compiler builds Alex Bennée
2020-10-02 11:36 ` [PULL 12/14] configure: Bump the minimum required Python version to 3.6 Alex Bennée
2020-10-02 11:36 ` [PULL 13/14] gitlab: move linux-user plugins test across to gitlab Alex Bennée
2020-10-02 11:36 ` [PULL 14/14] gitlab: split deprecated job into build/check stages Alex Bennée
2020-10-02 13:29 ` 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=CAFEAcA9DApaAdK21stVPab_8jYAUeHiR4AkVDzpnaTdx5xAuvQ@mail.gmail.com \
    --to=peter.maydell@linaro.org \
    --cc=alex.bennee@linaro.org \
    --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).