From: Jim Fehlig <jfehlig@suse.com>
To: Ian Campbell <ian.campbell@citrix.com>
Cc: wei.liu2@citrix.com, ian.jackson@eu.citrix.com, xen-devel@lists.xen.org
Subject: Re: [PATCH] docs: document handling of metacharacter escape in xl disk format
Date: Thu, 18 Feb 2016 15:44:37 -0700 [thread overview]
Message-ID: <56C64955.7000909@suse.com> (raw)
In-Reply-To: <1455793357-5712-1-git-send-email-ian.campbell@citrix.com>
Ian Campbell wrote:
> Signed-off-by: Ian Campbell <ian.campbell@citrix.com>
> Cc: Jim Fehlig <jfehlig@suse.com>
> ---
> docs/misc/xl-disk-configuration.txt | 18 ++++++++++++++++++
> 1 file changed, 18 insertions(+)
>
> diff --git a/docs/misc/xl-disk-configuration.txt b/docs/misc/xl-disk-configuration.txt
> index 6a2118d..a03ad10 100644
> --- a/docs/misc/xl-disk-configuration.txt
> +++ b/docs/misc/xl-disk-configuration.txt
> @@ -48,6 +48,24 @@ positionally or explicitly).
>
> Whitespace may appear before each parameter and will be ignored.
>
> +Metacharacters in a <diskspec> may be escaped using a backslash:
> +
> + Escape HEX Description
> + ------ --- -----------
> + \a 0x07 Bell
> + \b 0x08 Backspace
> + \t 0x09 Horizontal Tab
> + \n 0x0A New Line / Line Feed
> + \f 0x0C Form Feed
> + \r 0x0D Carriage Return
> + \v 0x0B Vertical Tab
> + \" 0x22 A literal double quote
> + \' 0x27 A literal single quote
> + \\ 0x5C A literal backslash
> + \xXX Character XX in hexadecimal
> + \OOO Character OOO in octal
Do you know how any of these would be useful in a diskspec? I guess I'm
struggling to understand when a 'Bell' would be needed :-).
Regards,
Jim
next prev parent reply other threads:[~2016-02-18 22:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-18 11:02 [PATCH] docs: document handling of metacharacter escape in xl disk format Ian Campbell
2016-02-18 22:44 ` Jim Fehlig [this message]
2016-02-19 10:14 ` Ian Campbell
2016-02-19 10:23 ` Ian Campbell
2016-02-24 11:56 ` Wei Liu
2016-02-19 16:11 ` Jim Fehlig
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=56C64955.7000909@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).