From: Fam Zheng <famz@redhat.com>
To: qemu-devel@nongnu.org
Cc: Kevin Wolf <kwolf@redhat.com>,
qemu-block@nongnu.org, Max Reitz <mreitz@redhat.com>
Subject: [Qemu-devel] [PATCH 0/2] block: Introduce "json-file:" protocol
Date: Tue, 3 Nov 2015 15:01:16 +0800 [thread overview]
Message-ID: <1446534078-11172-1-git-send-email-famz@redhat.com> (raw)
This would be a safer channel when we want to provide block options that
contain sensitive information, such as fields for authentication.
Fam Zheng (2):
block: Add "json-file:" pseudo protocol
iotests: Add tests for "json-file:" pseudo protocol
block.c | 58 +++++++++++++++++++++++++++++++++++++++++-----
tests/qemu-iotests/089 | 27 +++++++++++++++++----
tests/qemu-iotests/089.out | 15 ++++++++++++
3 files changed, 90 insertions(+), 10 deletions(-)
--
2.4.3
next reply other threads:[~2015-11-03 7:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-03 7:01 Fam Zheng [this message]
2015-11-03 7:01 ` [Qemu-devel] [PATCH 1/2] block: Add "json-file:" pseudo protocol Fam Zheng
2015-11-03 7:01 ` [Qemu-devel] [PATCH 2/2] iotests: Add tests for " Fam Zheng
2015-11-03 7:35 ` [Qemu-devel] [PATCH 0/2] block: Introduce "json-file:" protocol Daniel P. Berrange
2015-11-03 7:56 ` Fam Zheng
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=1446534078-11172-1-git-send-email-famz@redhat.com \
--to=famz@redhat.com \
--cc=kwolf@redhat.com \
--cc=mreitz@redhat.com \
--cc=qemu-block@nongnu.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).