All of lore.kernel.org
 help / color / mirror / Atom feed
From: Keir Fraser <keir.fraser@eu.citrix.com>
To: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Future of xenbits Linux trees
Date: Thu, 04 Jun 2009 16:45:26 +0100	[thread overview]
Message-ID: <C64DAAA6.788E%keir.fraser@eu.citrix.com> (raw)

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

             reply	other threads:[~2009-06-04 15:45 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-04 15:45 Keir Fraser [this message]
2009-06-04 16:09 ` Future of xenbits Linux trees Jean Guyader
2009-06-04 16:16 ` Tim Post
2009-06-04 18:08 ` Espen Skoglund
2009-06-04 18:17   ` Keir Fraser
2009-06-04 18:21     ` Jean Guyader
2009-06-05  7:32 ` Andrew Lyon
2009-06-05  7:46   ` Pasi Kärkkäinen
2009-06-05  7:52   ` Keir Fraser
2009-06-05  7:58   ` Jean Guyader
2009-06-05  8:30     ` Pasi Kärkkäinen
2009-06-05 18:51   ` Andy Burns
2009-06-07 17:09     ` Pasi Kärkkäinen
2009-06-07 18:36       ` M A Young
2009-06-07 18:52       ` Andy Burns
2009-06-05 13:26 ` Christian Tramnitz
2009-06-05 13:36   ` Keir Fraser
2009-06-05 14:05     ` Dulloor
2009-06-05 14:37       ` Ian Pratt
2009-06-05 17:13         ` Gerd Hoffmann
2009-06-05 14:05     ` Christian Tramnitz
2009-06-05 16:41     ` Gerd Hoffmann
2009-06-05 17:58       ` AW: " Carsten Schiers
2009-06-05 18:49         ` Keir Fraser
2009-06-05 21:02           ` AW: " Carsten Schiers
  -- strict thread matches above, loose matches on Subject: below --
2009-06-04 18:01 Boris Derzhavets
2009-06-04 18:46 ` Jean Guyader
2009-06-04 19:08   ` Keir Fraser
2009-06-04 19:13     ` Jean Guyader
2009-06-05  7:37 Boris Derzhavets
2009-06-05  7:53 Boris Derzhavets
2009-06-05 23:05 ` Genki Kuroda
2009-06-06  2:17   ` Kamala Narasimhan
2009-06-06  2:48     ` Genki Kuroda
2009-06-06  2:53       ` Kamala Narasimhan
2009-06-06  5:26         ` Genki Kuroda
2009-06-06  9:54           ` Jean Guyader
2009-06-05 10:44 Boris Derzhavets
2009-06-06 20:11 Boris Derzhavets

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=C64DAAA6.788E%keir.fraser@eu.citrix.com \
    --to=keir.fraser@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.