From mboxrd@z Thu Jan 1 00:00:00 1970 From: Keir Fraser Subject: Future of xenbits Linux trees Date: Thu, 04 Jun 2009 16:45:26 +0100 Message-ID: Mime-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit Return-path: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: "xen-devel@lists.xensource.com" List-Id: xen-devel@lists.xenproject.org Folks, With 3.4 out the door it is time to revisit the state of our Linux repositories. Currently we have a number of trees in various states of maintenance: - linux-2.6.18-xen.hg: the 'original' tree. Still maintained, used and tested but increasingly long in the tooth. - ext/linux-2.6.27-xen.hg: a snapshot of opensuse's kernel port. This clones tree is not maintained or tested. - XCI/linux-2.6.27.git: a forward port of the Xen patches to 2.6.27. Maintained as part of XCI project. - Jeremy's pv_ops patches against kernel.org: maintained, (somewhat) tested, but incomplete. It is probably time to kill the 2.6.18 tree, or at least stop active development within it. It is increasingly a kludged collection of backports of more recent kernel patches, and is also missing a lot of drivers for more modern hardware. Our proposal is to move XCI's linux-2.6.27 tree out of the XCI subproject and make it the main user tree. Development and automated testing would occur on that tree and of course on Jeremy's pv_ops patchset (which we want to completely move onto at some point in the future). What do people think of this as a plan? -- Keir