From: Hongyang Yang <yanghy@cn.fujitsu.com>
To: Wei Liu <wei.liu2@citrix.com>, xen-devel@lists.xen.org
Cc: Shriram Rajagopalan <rshriram@cs.ubc.ca>,
Ian Jackson <ian.jackson@eu.citrix.com>,
Ian Campbell <ian.campbell@citrix.com>
Subject: Re: [PATCH] README: point to correct location of README.remus
Date: Mon, 20 Oct 2014 20:11:50 +0800 [thread overview]
Message-ID: <5444FC06.9060702@cn.fujitsu.com> (raw)
In-Reply-To: <1413740910-1116-1-git-send-email-wei.liu2@citrix.com>
在 10/20/2014 01:48 AM, Wei Liu 写道:
> The said file was moved in 20857ac ("remus: move remus README to docs
> directory").
>
> Signed-off-by: Wei Liu <wei.liu2@citrix.com>
> Cc: Ian Campbell <ian.campbell@citrix.com>
> Cc: Ian Jackson <ian.jackson@eu.citrix.com>
> Cc: Yang Hongyang <yanghy@cn.fujitsu.com>
> Cc: Shriram Rajagopalan <rshriram@cs.ubc.ca>
Acked-by: Yang Hongyang <yanghy@cn.fujitsu.com>
> ---
> README | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/README b/README
> index e860644..8162ec9 100644
> --- a/README
> +++ b/README
> @@ -75,7 +75,7 @@ disabled at compile time:
> * systemd daemon development files
> * Development install of libnl3 (e.g., libnl-3-200,
> libnl-3-dev, etc). Required if network buffering is desired
> - when using Remus with libxl. See tools/remus/README for detailed
> + when using Remus with libxl. See docs/README.remus for detailed
> information.
>
> Second, you need to acquire a suitable kernel for use in domain 0. If
>
--
Thanks,
Yang.
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2014-10-20 12:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-19 17:48 [PATCH] README: point to correct location of README.remus Wei Liu
2014-10-20 12:11 ` Hongyang Yang [this message]
2014-10-20 13:20 ` 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=5444FC06.9060702@cn.fujitsu.com \
--to=yanghy@cn.fujitsu.com \
--cc=ian.campbell@citrix.com \
--cc=ian.jackson@eu.citrix.com \
--cc=rshriram@cs.ubc.ca \
--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 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.