From: Wei Liu <wei.liu2@citrix.com>
To: Ian Jackson <ian.jackson@eu.citrix.com>
Cc: Xen-devel <xen-devel@lists.xenproject.org>,
Wei Liu <wei.liu2@citrix.com>,
zhangchen.fnst@cn.fujitsu.com, yi.y.sun@linux.intel.com,
haozhong.zhang@intel.com
Subject: Re: [PATCH 0/2] tools: split xl into a separate directory
Date: Thu, 23 Feb 2017 13:20:25 +0000 [thread overview]
Message-ID: <20170223132025.ifemmy7jx4upnhqd@citrix.com> (raw)
In-Reply-To: <22702.53986.350510.805344@mariner.uk.xensource.com>
On Thu, Feb 23, 2017 at 12:17:38PM +0000, Ian Jackson wrote:
> Wei Liu writes ("[PATCH 0/2] tools: split xl into a separate directory"):
> > Xl has grown sufficiently large to warrnant its own directory. We also need
> > clear separation between the client (xl) and library (libxl).
>
> This is a fine idea.
>
> Both patches,
>
> Acked-by: Ian Jackson <ian.jackson@eu.citrix.com>
>
Hmm... It turns out the build system needs a bit more attention.
Parallel build failed. I will rework and resend.
Wei.
> Thanks,
> Ian.
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
next prev parent reply other threads:[~2017-02-23 13:20 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-21 15:51 [PATCH 0/2] tools: split xl into a separate directory Wei Liu
2017-02-21 15:51 ` [PATCH 1/2] tools: provide libxlutil compiling and linking options Wei Liu
2017-02-21 15:51 ` [PATCH 2/2] tools: move xl to a dedicated directory Wei Liu
2017-02-23 12:17 ` [PATCH 0/2] tools: split xl into a separate directory Ian Jackson
2017-02-23 13:20 ` Wei Liu [this message]
2017-02-23 14:55 ` Wei Liu
2017-02-23 15:54 ` Ian Jackson
2017-02-23 15:57 ` Wei Liu
2017-02-23 16:29 ` Ian Jackson
2017-02-23 16:59 ` Wei Liu
2017-02-23 17:01 ` Wei Liu
2017-02-23 17:25 ` Ian Jackson
2017-02-23 17:27 ` 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=20170223132025.ifemmy7jx4upnhqd@citrix.com \
--to=wei.liu2@citrix.com \
--cc=haozhong.zhang@intel.com \
--cc=ian.jackson@eu.citrix.com \
--cc=xen-devel@lists.xenproject.org \
--cc=yi.y.sun@linux.intel.com \
--cc=zhangchen.fnst@cn.fujitsu.com \
/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.