qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Fam Zheng <famz@redhat.com>
To: qemu-devel@nongnu.org
Cc: Peter Maydell <peter.maydell@linaro.org>
Subject: [Qemu-devel] [PULL 0/2] Docker patches for 2.9
Date: Fri, 10 Mar 2017 15:20:49 +0800	[thread overview]
Message-ID: <20170310072051.15704-1-famz@redhat.com> (raw)

The following changes since commit eba44e9339fc13c36e24c8c59e2b73ea231b46a1:

  Merge remote-tracking branch 'remotes/jasowang/tags/net-pull-request' into staging (2017-03-06 15:13:23 +0000)

are available in the git repository at:

  git://github.com/famz/qemu.git tags/docker-pull-request

for you to fetch changes up to 8ba1e5f72b17584f23e17c54494bb4beeb05174e:

  docker/dockerfiles/debian-s390-cross: include clang (2017-03-10 15:05:22 +0800)

----------------------------------------------------------------

Hi Peter, here are two more docker patches:

- Fix for shippable.
- Improvement on proxy env var. Technically it's not a fix but since it's under
  tests/, it doesn't have to wait for the 2.10 window.

----------------------------------------------------------------

Alex Bennée (1):
  docker/dockerfiles/debian-s390-cross: include clang

Philippe Mathieu-Daudé (1):
  tests/docker: support proxy / corporate firewall

 tests/docker/docker.py                             | 6 ++++++
 tests/docker/dockerfiles/debian-s390x-cross.docker | 4 ++--
 2 files changed, 8 insertions(+), 2 deletions(-)

-- 
2.9.3

             reply	other threads:[~2017-03-10  7:21 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-10  7:20 Fam Zheng [this message]
2017-03-10  7:20 ` [Qemu-devel] [PULL 1/2] tests/docker: support proxy / corporate firewall Fam Zheng
2017-03-10  7:20 ` [Qemu-devel] [PULL 2/2] docker/dockerfiles/debian-s390-cross: include clang Fam Zheng
2017-03-13 13:16 ` [Qemu-devel] [PULL 0/2] Docker patches for 2.9 Peter Maydell

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=20170310072051.15704-1-famz@redhat.com \
    --to=famz@redhat.com \
    --cc=peter.maydell@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).