All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Xen-devel <xen-devel@lists.xensource.com>
Subject: xen.git branches
Date: Wed, 03 Mar 2010 10:04:46 -0800	[thread overview]
Message-ID: <4B8EA4BE.5050402@goop.org> (raw)

Another month, another branch shuffle to confuse everyone ;)

I've added a couple of new branches:

    * xen/stable-2.6.31.x - This is currently identical to xen/master. 
      As its name suggests, it is going to track the 2.6.31.x stable
      tree.  I don't think there'll be any more 2.6.31.x kernels
      released, so this will just have Xen-related bugfixes.  Required
      for pre-Xen 4/3.4.3.
    * xen/stable-2.6.32.x - This is currently an alias of xen/stable. 
      2.6.32 is going to be a long-term maintained kernel, so this
      branch will likely be active for a long time.  It will get both
      Linux updates and Xen bugfixes+features.  Requires Xen 4 or 3.4.3.

So what about the other branches?

    * xen/stable - will always be the most recent "stable" kernel.  For
      now it will track stable-2.6.32.x, but when we move the main
      development focus to 2.6.33 and beyond, it will track that stable
      kernel.  It will be the default branch for xen.git.
    * xen/master - I haven't quite worked out what to do with this in
      the medium term.  I'm thinking that I'll make xen/master an alias
      for xen/stable, since people are already using it as a default
      branch.  At the moment its still stable-2.6.31.x.
    * xen/next - Active development branch.  Generally bleeding-edge.


I'm not quite ready to move xen/next into bleeding-edge phase yet.  The 
2.6.32 tree is still missing a few things and needs more testing before 
I'm happy with it.

     J

             reply	other threads:[~2010-03-03 18:04 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-03 18:04 Jeremy Fitzhardinge [this message]
2010-03-04  7:18 ` xen.git branches Fantu
2010-03-04 18:25   ` Jeremy Fitzhardinge
2010-03-04 18:20     ` Konrad Rzeszutek Wilk
2010-03-04 18:48       ` Jeremy Fitzhardinge
2010-03-04 19:24     ` Sander Eikelenboom
2010-03-04 20:10       ` Jeremy Fitzhardinge
2010-03-05  0:29         ` Noboru Iwamatsu
2010-03-05  7:26           ` Pasi Kärkkäinen
2010-03-18 23:19           ` xen.git branches / pvops kernel pvusb support Pasi Kärkkäinen
2010-03-18 23:33             ` Jeremy Fitzhardinge
2010-04-12 13:05             ` Pasi Kärkkäinen
2010-06-07 14:59               ` Pasi Kärkkäinen
2010-06-07 15:07                 ` Sander Eikelenboom
2010-08-17 19:00                 ` porting pvusb drivers to pvops kernel Pasi Kärkkäinen
2010-08-17 22:08                   ` Sander Eikelenboom
2010-08-18  0:52                     ` Noboru Iwamatsu
2010-08-18  0:08                   ` James Harper
2010-08-18  6:28                     ` Pasi Kärkkäinen

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=4B8EA4BE.5050402@goop.org \
    --to=jeremy@goop.org \
    --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.