From: Eric Blake <eblake@redhat.com>
To: qemu-devel@nongnu.org
Cc: nsoffer@redhat.com,
Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com>,
v.sementsov-og@ya.ru, rjones@redhat.com, qemu-block@nongnu.org
Subject: [PATCH v3 1/3] docs: Consistent typography for options of qemu-nbd
Date: Mon, 14 Mar 2022 15:38:16 -0500 [thread overview]
Message-ID: <20220314203818.3681277-2-eblake@redhat.com> (raw)
In-Reply-To: <20220314203818.3681277-1-eblake@redhat.com>
Prefer the :option:`--name` form when cross-referencing other options
from the qemu-nbd documentation.
Signed-off-by: Eric Blake <eblake@redhat.com>
---
docs/tools/qemu-nbd.rst | 12 ++++++------
1 file changed, 6 insertions(+), 6 deletions(-)
diff --git a/docs/tools/qemu-nbd.rst b/docs/tools/qemu-nbd.rst
index 2b8c90c35498..4c950f61998e 100644
--- a/docs/tools/qemu-nbd.rst
+++ b/docs/tools/qemu-nbd.rst
@@ -27,7 +27,7 @@ Options
.. program:: qemu-nbd
*filename* is a disk image filename, or a set of block
-driver options if ``--image-opts`` is specified.
+driver options if :option:`--image-opts` is specified.
*dev* is an NBD device.
@@ -165,9 +165,9 @@ driver options if ``--image-opts`` is specified.
.. option:: --tls-creds=ID
Enable mandatory TLS encryption for the server by setting the ID
- of the TLS credentials object previously created with the --object
- option; or provide the credentials needed for connecting as a client
- in list mode.
+ of the TLS credentials object previously created with the
+ :option:`--object` option; or provide the credentials needed for
+ connecting as a client in list mode.
.. option:: --tls-hostname=hostname
@@ -176,11 +176,11 @@ driver options if ``--image-opts`` is specified.
against information in the server provided certificate. Sometimes
it might be required to override the hostname used to perform this
check. For example, if the NBD client is using a tunnel from localhost
- to connect to the remote server, the `--tls-hostname` option should
+ to connect to the remote server, the :option:`--tls-hostname` option should
be used to set the officially expected hostname of the remote NBD
server. This can also be used if accessing NBD over a UNIX socket
where there is no inherent hostname available. This is only permitted
- when acting as a NBD client with the `--list` option.
+ when acting as a NBD client with the :option:`--list` option.
.. option:: --fork
--
2.35.1
next prev parent reply other threads:[~2022-03-14 20:41 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-14 20:38 [PATCH v3 0/3] nbd: MULTI_CONN for shared writable exports Eric Blake
2022-03-14 20:38 ` Eric Blake [this message]
2022-03-17 8:15 ` [PATCH v3 1/3] docs: Consistent typography for options of qemu-nbd Daniel P. Berrangé
2022-03-14 20:38 ` [PATCH v3 2/3] qemu-nbd: Pass max connections to blockdev layer Eric Blake
2022-03-14 20:38 ` [PATCH v3 3/3] nbd/server: Allow MULTI_CONN for shared writable exports Eric Blake
2022-03-15 13:14 ` Richard W.M. Jones
2022-03-16 21:07 ` Eric Blake
2022-03-16 21:15 ` Eric Blake
2022-03-16 23:01 ` Richard W.M. Jones
2022-04-27 15:52 ` Kevin Wolf
2022-04-27 21:39 ` Eric Blake
2022-04-29 12:49 ` Kevin Wolf
2022-05-02 21:12 ` Eric Blake
2022-05-03 7:56 ` Kevin Wolf
2022-04-22 20:23 ` [PATCH v3 0/3] nbd: " Eric Blake
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=20220314203818.3681277-2-eblake@redhat.com \
--to=eblake@redhat.com \
--cc=nsoffer@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=rjones@redhat.com \
--cc=v.sementsov-og@ya.ru \
--cc=vsementsov@virtuozzo.com \
/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).