From: "Marek Marczykowski-Górecki" <marmarek@invisiblethingslab.com>
To: "Roger Pau Monné" <roger.pau@citrix.com>
Cc: Simon Gaiser <simon@invisiblethingslab.com>,
Ian Jackson <ian.jackson@eu.citrix.com>,
Wei Liu <wei.liu2@citrix.com>,
xen-devel@lists.xenproject.org, xen-devel@lists.xen.org
Subject: Re: [PATCH] xenstore-client: Add option for raw in-/output
Date: Mon, 23 Jul 2018 12:10:13 +0200 [thread overview]
Message-ID: <20180723101013.GG1371@mail-itl> (raw)
In-Reply-To: <20180723093905.crf63rc2ubah3ead@mac.bytemobile.com>
[-- Attachment #1.1: Type: text/plain, Size: 708 bytes --]
On Mon, Jul 23, 2018 at 11:39:05AM +0200, Roger Pau Monné wrote:
> On Sat, Jul 21, 2018 at 04:35:37PM +0200, Marek Marczykowski-Górecki wrote:
> > From: Simon Gaiser <simon@invisiblethingslab.com>
> >
> > Parsing/generating the escape sequences used by xenstore-client is non
> > trivial. So make scripting (for use in stubdom) easier by adding a raw
> > option.
>
> Should a description for this option be added to the man pages?
Yes, but I didn't found one for xenstore-read/xenstore-write. Where is
it?
--
Best Regards,
Marek Marczykowski-Górecki
Invisible Things Lab
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
[-- Attachment #2: Type: text/plain, Size: 157 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
next prev parent reply other threads:[~2018-07-23 10:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-21 14:35 [PATCH] xenstore-client: Add option for raw in-/output Marek Marczykowski-Górecki
2018-07-23 9:39 ` Roger Pau Monné
2018-07-23 10:10 ` Marek Marczykowski-Górecki [this message]
2018-07-25 9:21 ` Wei Liu
2018-07-25 9:20 ` Wei Liu
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=20180723101013.GG1371@mail-itl \
--to=marmarek@invisiblethingslab.com \
--cc=ian.jackson@eu.citrix.com \
--cc=roger.pau@citrix.com \
--cc=simon@invisiblethingslab.com \
--cc=wei.liu2@citrix.com \
--cc=xen-devel@lists.xen.org \
--cc=xen-devel@lists.xenproject.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.