From: Aron Griffis <aron@hp.com>
To: Keir Fraser <Keir.Fraser@cl.cam.ac.uk>
Cc: Anthony Liguori <aliguori@us.ibm.com>,
xen-devel <xen-devel@lists.xensource.com>
Subject: Re: Has 3.0.3 been released?
Date: Tue, 17 Oct 2006 18:26:40 -0400 [thread overview]
Message-ID: <20061017222639.GE27879@fc.hp.com> (raw)
In-Reply-To: <C15B0FD8.2AFB%Keir.Fraser@cl.cam.ac.uk>
Keir Fraser wrote: [Tue Oct 17 2006, 05:55:20PM EDT]
> > Will the tree structure change from the current sparse model to
> > a fully-populated kernel? IMHO it wouldn't be too hard to use
> > something similar to
> > http://xenbits.xensource.com/ext/linux-2.6.tip-xen.hg plus a top-level
> > xen directory containing the hypervisor. Alternatively, since Xen
> > isn't just Linux, maybe the hypervisor and kernels should be in
> > separate repositories?
>
> Perhaps. We might at least separate the kernel bits from the
> hypervisor bits. We like working with a sparse tree as it's much
> quicker than cloning entire Linux repos.
I suppose xen/include/public synchronization also poses a challenge,
unless it's okay for the kernel to #include files outside of the
kernel tree.
Aron
next prev parent reply other threads:[~2006-10-17 22:26 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-17 21:06 Has 3.0.3 been released? Anthony Liguori
2006-10-17 21:45 ` S.Çağlar Onur
2006-10-17 21:57 ` Steven Hand
2006-10-17 22:02 ` John Levon
2006-10-17 21:53 ` Keir Fraser
2006-10-17 22:20 ` Adam Heath
2006-10-17 22:32 ` Steven Hand
2006-10-18 6:43 ` Pasi Kärkkäinen
2006-10-18 7:00 ` Steven Hand
2006-10-17 22:01 ` Aron Griffis
2006-10-17 21:55 ` Keir Fraser
2006-10-17 22:26 ` Aron Griffis [this message]
2006-10-18 12:43 ` Markus Armbruster
2006-10-18 12:51 ` Keir Fraser
2006-10-18 13:06 ` Muli Ben-Yehuda
2006-10-18 13:25 ` Aron Griffis
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=20061017222639.GE27879@fc.hp.com \
--to=aron@hp.com \
--cc=Keir.Fraser@cl.cam.ac.uk \
--cc=aliguori@us.ibm.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.