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: Tue, 28 Feb 2017 20:44:56 +0800 [thread overview]
Message-ID: <20170228124458.31307-1-famz@redhat.com> (raw)
The following changes since commit 6181478f6395cdd9d6ffd99623d0c9f39ea53606:
Merge remote-tracking branch 'remotes/stefanha/tags/block-pull-request' into staging (2017-02-28 08:46:03 +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 1ed9251515382a1fc9c6187fee8d7d7bf141dc90:
.shippable: add s390x-cross target (2017-02-28 20:31:01 +0800)
----------------------------------------------------------------
Two more test/build automation patches from Alex for the freeze. Theoretically
these are okay to merge even after freeze but on the other hand I see no reason
to delay them.
----------------------------------------------------------------
Alex Bennée (2):
new: dockerfiles/debian-s390-cross
.shippable: add s390x-cross target
.shippable.yml | 2 ++
tests/docker/dockerfiles/debian-s390x-cross.docker | 22 ++++++++++++++++++++++
2 files changed, 24 insertions(+)
create mode 100644 tests/docker/dockerfiles/debian-s390x-cross.docker
--
2.9.3
next reply other threads:[~2017-02-28 12:45 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-28 12:44 Fam Zheng [this message]
2017-02-28 12:44 ` [Qemu-devel] [PULL 1/2] new: dockerfiles/debian-s390-cross Fam Zheng
2017-02-28 12:44 ` [Qemu-devel] [PULL 2/2] .shippable: add s390x-cross target Fam Zheng
2017-03-01 13:52 ` [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-11-10 13:42 Fam Zheng
2017-11-14 8:38 ` 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=20170228124458.31307-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).