From: Ian Campbell <ian.campbell@citrix.com>
To: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Cc: xen-devel@lists.xensource.com
Subject: Re: [ANNOUNCE] Project Raisin
Date: Thu, 2 Apr 2015 10:09:10 +0100 [thread overview]
Message-ID: <1427965750.4037.10.camel@citrix.com> (raw)
In-Reply-To: <alpine.DEB.2.02.1503282222350.9516@kaball.uk.xensource.com>
On Tue, 2015-03-31 at 11:16 +0100, Stefano Stabellini wrote:
> Hi all,
>
> A few weeks ago I started hacking on a new project, consisting in a set
> of bash scripts to build xen-unstable and a few other useful elements.
> It is still in very early stages.
>
> The name of the new project is "Raisin", from Raise Xen, pun intended
> ;-)
> It is a bit like DevStack[1] for Xen: its purpose is to simply and
> quickly retrieve and build Xen and any other related components from
> source, such as Libvirt and Grub2.
I think this is great and I look forward to it being integrated with
osstest so we can start moving 3rd party components out of xen.git
>From a UI point of view I think it would be useful to move as much
non-user-facing stuff as possible into a subdirectory such that a user
just gets something like:
$ ls
README raisin.sh* lib components
COPYING config
rather than being overwhelmed by all sorts of scripts etc.
I see you've moved the components into a subdir since the first posting.
which is good, I'd suggest to move as much of the other stuff
(common-funcitons, git-checkout, mk*) down a level too.
Ian.
prev parent reply other threads:[~2015-04-02 9:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-31 10:16 [ANNOUNCE] Project Raisin Stefano Stabellini
2015-04-01 13:04 ` George Dunlap
2015-04-01 15:13 ` Stefano Stabellini
2015-04-01 15:42 ` Ian Campbell
2015-04-01 20:19 ` George Dunlap
2015-04-02 14:25 ` Stefano Stabellini
2015-04-02 9:09 ` Ian Campbell [this message]
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=1427965750.4037.10.camel@citrix.com \
--to=ian.campbell@citrix.com \
--cc=stefano.stabellini@eu.citrix.com \
--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 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.