From: Jim Fehlig <jfehlig@suse.com>
To: Ian Campbell <ian.campbell@citrix.com>, xen-devel@lists.xen.org
Cc: wei.liu2@citrix.com, ian.jackson@eu.citrix.com
Subject: Re: [PATCH 3/3] docs: add more info about target= in disk config
Date: Wed, 17 Feb 2016 10:24:23 -0700 [thread overview]
Message-ID: <56C4ACC7.5090506@suse.com> (raw)
In-Reply-To: <1455703822.814.147.camel@citrix.com>
On 02/17/2016 03:10 AM, Ian Campbell wrote:
> On Tue, 2016-02-16 at 20:54 -0700, Jim Fehlig wrote:
>> target= in disk config can be used to convey arbitrary
>> configuration information to backends. Add a bit more info
>> to xl-disk-configuration.txt to clarify this, including some
>> simple nbd and rbd qdisk configurations.
> Missing S-o-b.
>
>> ---
>> docs/misc/xl-disk-configuration.txt | 10 +++++++++-
>> 1 file changed, 9 insertions(+), 1 deletion(-)
>>
>> diff --git a/docs/misc/xl-disk-configuration.txt b/docs/misc/xl-disk-
>> configuration.txt
>> index 29f6ddb..0918fb8 100644
>> --- a/docs/misc/xl-disk-configuration.txt
>> +++ b/docs/misc/xl-disk-configuration.txt
>> @@ -75,7 +75,15 @@ Special syntax:
>> the target was already specified as a positional parameter. This
>> is the only way to specify a target string containing metacharacters
>> such as commas and (in some cases) colons, which would otherwise be
>> - misinterpreted.
>> + misinterpreted. Meta-information in a target string can be used to
>> + specify configuration information for a qdisk block backend. For
>> + example the nbd and rbd qdisk block backends can be configured with
>> +
>> + target=nbd:192.168.0.1:5555
>> + target=rbd:pool/image:mon_host=192.186.0.1\\:6789
>> +
>> + Note the use of double backslash ('\\') for metacharacters that need
>> + escaped.
> "need to be escaped".
>
> However I wouldn't describe "\\" that way, I think I would say "note that \
> is used to escape metacharacters and therefore to get a literal backslash
> "\\" is required".
Agreed. I changed the text and sent a V2 of the series.
>
> The general concept of escaping metacharaters is not mentioned in this doc
> at all, i.e. there is no mention of which characters need such escaping nor
> of the various "special" codes (\t and \n etc), nor of the octal and hex
> escape codes. Maybe that's a topic for another patch though.
I could do that in a follow-up, but I have no clue what those mean or how they
are used.
Regards,
Jim
next prev parent reply other threads:[~2016-02-17 17:24 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-17 3:54 [PATCH 0/3] libxl and docs: small improvements in qdisk support Jim Fehlig
2016-02-17 3:54 ` [PATCH 1/3] libxlu_cfg: reject unknown characters following '\' Jim Fehlig
2016-02-17 10:05 ` Ian Campbell
2016-02-17 10:11 ` Ian Campbell
2016-02-17 17:26 ` Jim Fehlig
2016-02-17 3:54 ` [PATCH 2/3] docs: fix typo in xl-disk-configuration.txt Jim Fehlig
2016-02-17 10:05 ` Ian Campbell
2016-02-17 3:54 ` [PATCH 3/3] docs: add more info about target= in disk config Jim Fehlig
2016-02-17 10:10 ` Ian Campbell
2016-02-17 17:24 ` Jim Fehlig [this message]
2016-02-18 10:22 ` Ian Campbell
2016-02-19 17:23 ` Ian Jackson
2016-02-19 19:06 ` Jim Fehlig
2016-02-23 9:52 ` Ian Campbell
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=56C4ACC7.5090506@suse.com \
--to=jfehlig@suse.com \
--cc=ian.campbell@citrix.com \
--cc=ian.jackson@eu.citrix.com \
--cc=wei.liu2@citrix.com \
--cc=xen-devel@lists.xen.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).