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
Date: Fri, 10 Nov 2017 21:42:52 +0800	[thread overview]
Message-ID: <20171110134254.25031-1-famz@redhat.com> (raw)

The following changes since commit b0fbe46ad82982b289a44ee2495b59b0bad8a842:

  Update version for v2.11.0-rc0 release (2017-11-07 16:05:28 +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 6423795efc5b665c595d9a0bf93cfbbca00362e9:

  docker: correctly escape $BACKEND in the help output (2017-11-08 10:59:42 +0800)

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

Hi Peter,

Here are two fixes on docker testing (the one saying "improved" is to
make it actually "correct"). Thanks.

Fam

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

Fam Zheng (1):
  docker: Improved image checksum

Philippe Mathieu-Daudé (1):
  docker: correctly escape $BACKEND in the help output

 tests/docker/Makefile.include |  2 +-
 tests/docker/docker.py        | 24 +++++++++++++++++++++++-
 2 files changed, 24 insertions(+), 2 deletions(-)

-- 
2.13.6

             reply	other threads:[~2017-11-10 13:43 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-10 13:42 Fam Zheng [this message]
2017-11-10 13:42 ` [Qemu-devel] [PULL 1/2] docker: Improved image checksum Fam Zheng
2017-11-10 13:42 ` [Qemu-devel] [PULL 2/2] docker: correctly escape $BACKEND in the help output Fam Zheng
2017-11-14  8:38 ` [Qemu-devel] [PULL 0/2] Docker patches Peter Maydell
  -- strict thread matches above, loose matches on Subject: below --
2018-06-04  7:10 Fam Zheng
2018-06-04 14:46 ` Peter Maydell
2017-02-28 12:44 Fam Zheng
2017-03-01 13:52 ` Peter Maydell
2016-08-05  9:04 Fam Zheng
2016-08-05 10:44 ` 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=20171110134254.25031-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).