From: Keir Fraser <keir.fraser@eu.citrix.com>
To: M A Young <m.a.young@durham.ac.uk>,
Stefano Stabellini <Stefano.Stabellini@eu.citrix.com>,
Ian Campbell <Ian.Campbell@eu.citrix.com>
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 19:32:53 +0100 [thread overview]
Message-ID: <C86BAA65.1B25F%keir.fraser@eu.citrix.com> (raw)
In-Reply-To: <alpine.LFD.2.00.1007201858050.19930@vega3.dur.ac.uk>
Shouldn't this be in xen-unstable first, and then backported in the usual
way?
K.
On 20/07/2010 19:01, "M A Young" <m.a.young@durham.ac.uk> 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.
>
> Signed-off-by: Michael Young <m.a.young@durham.ac.uk>
>
> --- xen-4.0.1/tools/libxl/Makefile.orig 2010-07-16 18:27:14.000000000 +0100
> +++ xen-4.0.1/tools/libxl/Makefile 2010-07-16 19:39:46.000000000 +0100
> @@ -4,6 +4,7 @@
>
> XEN_ROOT = ../..
> include $(XEN_ROOT)/tools/Rules.mk
> +BASH_COMPLETION_DIR ?= /etc/bash_completion.d/
>
> MAJOR = 1.0
> MINOR = 0
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
next prev parent reply other threads:[~2010-07-20 18:32 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-20 18:01 [PATCH] Re: New release candidate for Xen 4.0.1 M A Young
2010-07-20 18:32 ` Keir Fraser [this message]
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
-- strict thread matches above, loose matches on Subject: below --
2010-07-16 13:05 Keir Fraser
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
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=C86BAA65.1B25F%keir.fraser@eu.citrix.com \
--to=keir.fraser@eu.citrix.com \
--cc=Ian.Campbell@eu.citrix.com \
--cc=Stefano.Stabellini@eu.citrix.com \
--cc=m.a.young@durham.ac.uk \
--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).