From: Keir Fraser <keir.fraser@eu.citrix.com>
To: "Pasi Kärkkäinen" <pasik@iki.fi>, "M A Young" <m.a.young@durham.ac.uk>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: [PATCH] Re: New release candidate for Xen 4.0.1
Date: Tue, 20 Jul 2010 13:30:26 +0100 [thread overview]
Message-ID: <C86B5572.1B0F0%keir.fraser@eu.citrix.com> (raw)
In-Reply-To: <20100720120140.GY17817@reaktio.net>
On 20/07/2010 13:01, "Pasi Kärkkäinen" <pasik@iki.fi> wrote:
> On Fri, Jul 16, 2010 at 08:29:09PM +0100, M A Young wrote:
>> I have a minor fix for this. BASH_COMPLETION_DIR is used uninitialized in
>> tools/libxl/Makefile which means that xl.sh can end up in / which is not
>> ideal. The patch below sets a sensible default for this variable.
>>
>
> Yeah, I noticed this problem aswell. This patch should go into
> xen-4.0-testing.hg.
I am not the person to Cc on toolstack patches. Ian and Stefano and
responsible for applying tools patches to xen-unstable and backporting to
stable branches.
-- Keir
next prev parent reply other threads:[~2010-07-20 12:30 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-16 13:05 New release candidate for Xen 4.0.1 Keir Fraser
2010-07-16 13:28 ` Pasi Kärkkäinen
2010-07-16 13:54 ` Keir Fraser
2010-07-20 11:57 ` Pasi Kärkkäinen
2010-07-20 12:21 ` Boris Derzhavets
2010-07-16 19:29 ` [PATCH] " M A Young
2010-07-20 12:01 ` Pasi Kärkkäinen
2010-07-20 12:30 ` Keir Fraser [this message]
-- strict thread matches above, loose matches on Subject: below --
2010-07-20 18:01 M A Young
2010-07-20 18:32 ` Keir Fraser
2010-07-21 9:42 ` M A Young
2010-07-21 10:23 ` Keir Fraser
2010-07-21 16:30 ` Dan Magenheimer
2010-07-21 16:46 ` Keir Fraser
2010-07-23 15:49 ` Ian Jackson
2010-07-21 11:53 ` Stefano Stabellini
2010-07-21 12:08 ` M A Young
2010-07-21 12:14 ` Stefano Stabellini
2010-07-21 12:48 ` Keir Fraser
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=C86B5572.1B0F0%keir.fraser@eu.citrix.com \
--to=keir.fraser@eu.citrix.com \
--cc=m.a.young@durham.ac.uk \
--cc=pasik@iki.fi \
--cc=xen-devel@lists.xensource.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 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).