From: Eric Blake <eblake@redhat.com>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] [PULL v2 0/3] NBD patches for 2019-02-25
Date: Tue, 26 Feb 2019 10:50:10 -0600 [thread overview]
Message-ID: <20190226165013.24867-1-eblake@redhat.com> (raw)
The following changes since commit d88d85f1f0625d57e9f354aa0874c4c8b5d1fb47:
Merge remote-tracking branch 'remotes/stefanha/tags/block-pull-request' into staging (2019-02-25 17:28:04 +0000)
are available in the Git repository at:
https://repo.or.cz/qemu/ericb.git tags/pull-nbd-2019-02-25-v2
for you to fetch changes up to 3e6f45446b11ccc20b4b751f70331f03d70369b8:
iotests: avoid broken pipe with certtool (2019-02-26 10:45:37 -0600)
(v2: pull in Andrey's v3 python patch per last-minute list emails)
----------------------------------------------------------------
nbd patches for 2019-02-25
- iotest failure fixes for tests related to NBD
----------------------------------------------------------------
Andrey Shinkevich (1):
iotests: handle TypeError for Python 3 in test 242
Daniel P. Berrangé (2):
iotests: ensure we print nbd server log on error
iotests: avoid broken pipe with certtool
tests/qemu-iotests/common.tls | 48 ++++++++++++++++++++++++++++---------------
tests/qemu-iotests/233 | 3 +++
tests/qemu-iotests/242 | 8 +++++---
3 files changed, 40 insertions(+), 19 deletions(-)
--
2.20.1
next reply other threads:[~2019-02-26 16:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-26 16:50 Eric Blake [this message]
2019-02-26 16:50 ` [Qemu-devel] [PULL v2 1/3] iotests: handle TypeError for Python 3 in test 242 Eric Blake
2019-02-26 16:50 ` [Qemu-devel] [PULL v2 2/3] iotests: ensure we print nbd server log on error Eric Blake
2019-02-26 16:50 ` [Qemu-devel] [PULL v2 3/3] iotests: avoid broken pipe with certtool Eric Blake
2019-02-28 12:59 ` [Qemu-devel] [PULL v2 0/3] NBD patches for 2019-02-25 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=20190226165013.24867-1-eblake@redhat.com \
--to=eblake@redhat.com \
--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).