From: Keir Fraser <keir@xensource.com>
To: Ian Pratt <m+Ian.Pratt@cl.cam.ac.uk>,
Sean Dague <japh@us.ibm.com>, Keir Fraser <keir@xensource.com>
Cc: xen-devel@lists.xensource.com
Subject: Re: Re: [ANNOUNCEMENT] Schedule for Xen 3.0.4
Date: Thu, 30 Nov 2006 09:05:21 +0000 [thread overview]
Message-ID: <C1944F51.5479%keir@xensource.com> (raw)
In-Reply-To: <8A87A9A84C201449A0C56B728ACF491E01FA34@liverpoolst.ad.cl.cam.ac.uk>
On 29/11/06 21:36, "Ian Pratt" <m+Ian.Pratt@cl.cam.ac.uk> wrote:
> We really need to get away from having a linux tree in xen-unstable
> anyhow. It would be cool if by the time that 3.0.4 goes out we have the
> out-of-tree linux 2.6.18/19 level up to the same spec as our 2.6.16. We
> can update the top-level Makefiles to make it very easy to build
> out-of-tree kernels. We can also make 2.6.18 RPMs and tar balls
> available for download. None of this actually has to be directly coupled
> to the 3.0.4 release.
Yes, we really should decouple Xen releases from guest-OS development.
-- Keir
next prev parent reply other threads:[~2006-11-30 9:05 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-24 10:28 [ANNOUNCEMENT] Schedule for Xen 3.0.4 Keir Fraser
2006-11-24 10:42 ` John Levon
2006-11-24 10:58 ` Ewan Mellor
2006-11-24 15:54 ` Daniel P. Berrange
2006-11-24 16:34 ` Ewan Mellor
2006-11-24 18:22 ` Daniel P. Berrange
2006-11-28 14:26 ` Ewan Mellor
2006-11-28 14:37 ` Daniel P. Berrange
2006-11-29 17:12 ` Daniel P. Berrange
2006-11-24 12:44 ` Jan Beulich
2006-11-24 18:26 ` Chuck Short
2006-11-29 15:31 ` Sean Dague
2006-11-29 21:36 ` Ian Pratt
2006-11-30 9:05 ` Keir Fraser [this message]
2006-11-30 14:59 ` Pasi Kärkkäinen
2006-11-30 15:02 ` Keir Fraser
2006-11-30 15:08 ` Pasi Kärkkäinen
2006-11-30 16:57 ` Keir Fraser
2006-11-30 17:27 ` Ian Pratt
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=C1944F51.5479%keir@xensource.com \
--to=keir@xensource.com \
--cc=japh@us.ibm.com \
--cc=m+Ian.Pratt@cl.cam.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 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.