On Fri, Feb 24, 2006 at 05:41:53PM +0100, Isaac Clerencia wrote: Hi,
> I agree. I just would like to ask that, please, don't disband just because of > disagreement with the kernel team, but try to cooperate anyway. > I don't think we want to! And I hope there is no disagreement (we still don't know)! The reason I think xen would be better served having its own committed team, repository, etc, is that it would be easier for anyone interested in xen to follow just mailing lists dedicated to it and its repository commits, rather than having to closely follow all the linux kernel work, mailing list, etc! Of course I also think it's great to have some people on both, so to have a close coordination between the xen and kernel releases. Also the xen team would need to coordinate with the glibc team (for the segmentation issues) and one day with the d-i team too, in order to try making a Debian/GNU/Xen/Linux (or whatever that should be called) installable directly on a system! Even upstream considers the linux kernel patch, the hypervisor and the tools separate, has separate mailing lists for them, and a separate mercurial repository for linux, even if for now they distribute the linux patch together with xen, until xen is merged into Linus' tree (or at least so Ian Pratt has said). If we can have the xen patch included in the debian kernel, thus pre-dating kernel.org inclusion that's really a good thing! Thanks! Guido -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
