From: Luiz Capitulino <lcapitulino@redhat.com>
To: qemu-devel@nongnu.org
Cc: aliguori@us.ibm.com, Alon Levy <alevy@redhat.com>
Subject: [Qemu-devel] [PATCH 2/3] qapi-schema: fix typos and explain 'spice' auth
Date: Fri, 9 Mar 2012 17:55:18 -0300 [thread overview]
Message-ID: <1331326519-12444-3-git-send-email-lcapitulino@redhat.com> (raw)
In-Reply-To: <1331326519-12444-1-git-send-email-lcapitulino@redhat.com>
From: Alon Levy <alevy@redhat.com>
Signed-off-by: Alon Levy <alevy@redhat.com>
Signed-off-by: Luiz Capitulino <lcapitulino@redhat.com>
---
qapi-schema.json | 14 ++++++++------
1 file changed, 8 insertions(+), 6 deletions(-)
diff --git a/qapi-schema.json b/qapi-schema.json
index 5f293c4..93ee2a4 100644
--- a/qapi-schema.json
+++ b/qapi-schema.json
@@ -616,11 +616,12 @@
# @connection-id: SPICE connection id number. All channels with the same id
# belong to the same SPICE session.
#
-# @connection-type: SPICE channel type number. "1" is the main control channel,
-# filter for this one if you want track spice sessions only
+# @connection-type: SPICE channel type number. "1" is the main control
+# channel, filter for this one if you want to track spice
+# sessions only
#
-# @channel-id: SPICE channel ID number. Usually "0", might be different needed
-# when multiple channels of the same type exist, such as multiple
+# @channel-id: SPICE channel ID number. Usually "0", might be different when
+# multiple channels of the same type exist, such as multiple
# display channels in a multihead setup
#
# @tls: true if the channel is encrypted, false otherwise.
@@ -649,8 +650,9 @@
# @tls-port: #optional The SPICE server's TLS port number.
#
# @auth: #optional the current authentication type used by the server
-# 'none' if no authentication is being used
-# 'spice' (TODO: describe)
+# 'none' if no authentication is being used
+# 'spice' uses SASL or direct TLS authentication, depending on command
+# line options
#
# @channels: a list of @SpiceChannel for each active spice channel
#
--
1.7.9.2.384.g4a92a
next prev parent reply other threads:[~2012-03-09 20:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-09 20:55 [Qemu-devel] [PULL 0/3]: QMP queue Luiz Capitulino
2012-03-09 20:55 ` [Qemu-devel] [PATCH 1/3] qjson.h: include compiler.h for GCC_FMT_ATTR Luiz Capitulino
2012-03-09 20:55 ` Luiz Capitulino [this message]
2012-03-09 20:55 ` [Qemu-devel] [PATCH 3/3] qapi-schema.json: fix comment for type ObjectPropretyInfo Luiz Capitulino
2012-03-13 2:22 ` [Qemu-devel] [PULL 0/3]: QMP queue Anthony Liguori
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=1331326519-12444-3-git-send-email-lcapitulino@redhat.com \
--to=lcapitulino@redhat.com \
--cc=alevy@redhat.com \
--cc=aliguori@us.ibm.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).