From: Fam Zheng <famz@redhat.com>
To: qemu-devel@nongnu.org
Cc: peter.maydell@linaro.org, Fam Zheng <famz@redhat.com>
Subject: [Qemu-devel] [PULL 0/4] Testing patches
Date: Mon, 9 Apr 2018 15:19:30 +0800 [thread overview]
Message-ID: <20180409071934.20845-1-famz@redhat.com> (raw)
The following changes since commit 08e173f29461396575c85510eb41474b993cb1fb:
Merge remote-tracking branch 'remotes/berrange/tags/qcrypto-next-pull-request' into staging (2018-04-06 17:51:21 +0100)
are available in the Git repository at:
git://github.com/famz/qemu.git tags/testing-pull-request
for you to fetch changes up to 07fed474177a4566052ea81b1563d53a37083e84:
docker: fedora: test more components (2018-04-09 15:13:02 +0800)
----------------------------------------------------------------
Testing patches
----------------------------------------------------------------
Fam Zheng (2):
tests: Fix ubuntu.i386 image initialization
docker: Inline "prep_fail" in run script
Paolo Bonzini (1):
docker: fedora: test more components
Philippe Mathieu-Daudé (1):
docker: dump 'config.log' if ./configure fails
tests/docker/common.rc | 4 +++-
tests/docker/dockerfiles/fedora.docker | 13 ++++++++++---
tests/docker/run | 2 +-
tests/vm/basevm.py | 5 +----
4 files changed, 15 insertions(+), 9 deletions(-)
--
2.14.3
next reply other threads:[~2018-04-09 7:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-09 7:19 Fam Zheng [this message]
2018-04-09 7:19 ` [Qemu-devel] [PULL 1/4] docker: dump 'config.log' if ./configure fails Fam Zheng
2018-04-09 7:19 ` [Qemu-devel] [PULL 2/4] tests: Fix ubuntu.i386 image initialization Fam Zheng
2018-04-09 7:19 ` [Qemu-devel] [PULL 3/4] docker: Inline "prep_fail" in run script Fam Zheng
2018-04-09 7:19 ` [Qemu-devel] [PULL 4/4] docker: fedora: test more components Fam Zheng
2018-04-09 11:02 ` [Qemu-devel] [PULL 0/4] Testing patches 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=20180409071934.20845-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).