xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Juergen Gross <jgross@suse.com>
To: Andrew Cooper <andrew.cooper3@citrix.com>,
	Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Cc: xen-devel@lists.xenproject.org, ian.jackson@eu.citrix.com,
	jbeulich@suse.com, stefano.stabellini@eu.citrix.com
Subject: Re: [PATCH] docs: add misc/qemu-backends.txt
Date: Mon, 11 Apr 2016 07:01:48 +0200	[thread overview]
Message-ID: <570B2FBC.6020705@suse.com> (raw)
In-Reply-To: <5707F820.6010708@citrix.com>

On 08/04/16 20:27, Andrew Cooper wrote:
> 
>>>> +Xenstore the backend information is presented there. <qemu> is built
>>> That looks to be missing an verb, no it has a verb, something is off with
>>> that.
>>>
>>> XenStore presents the backend information there?
>> No, qemu is presenting the information in Xenstore.
> 
> "Xenstore" is not the start of the sentence - it follows on from the
> previous line, but even as a native English speaker it took me a while
> to figure out.
> 
> A comma should be present (i.e. "As $FOO, $BAR relating to $FOO"), and
> it would aid clarity.
> 
> +As each qemu instance owns a path (named "<qemu>" from now on) in
> +Xenstore, the backend information is presented there. <qemu> is built

Will do it.


Juergen


_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel

  reply	other threads:[~2016-04-11  5:01 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-07  6:24 [PATCH] docs: add misc/qemu-backends.txt Juergen Gross
2016-04-08 14:54 ` Konrad Rzeszutek Wilk
2016-04-08 18:20   ` Juergen Gross
2016-04-08 18:27     ` Andrew Cooper
2016-04-11  5:01       ` Juergen Gross [this message]
2016-04-10 20:00 ` Stefano Stabellini
2016-04-11  4:52   ` Juergen Gross
2016-04-11 10:33   ` Wei Liu
2016-04-11 10:57     ` Juergen Gross
2016-04-11 12:05       ` 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=570B2FBC.6020705@suse.com \
    --to=jgross@suse.com \
    --cc=andrew.cooper3@citrix.com \
    --cc=ian.jackson@eu.citrix.com \
    --cc=jbeulich@suse.com \
    --cc=konrad.wilk@oracle.com \
    --cc=stefano.stabellini@eu.citrix.com \
    --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 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).