All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Jan Beulich <JBeulich@novell.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: master branch of xen.git
Date: Tue, 10 Aug 2010 23:45:09 -0700	[thread overview]
Message-ID: <4C6246F5.70309@goop.org> (raw)
In-Reply-To: <4C626189020000780000F382@vpn.id2.novell.com>

  On 08/10/2010 11:38 PM, Jan Beulich wrote:
> what's the disposition of the master branch of that tree? It doesn't
> seem to have seen any update during the last couple of months,
> and it's still 2.6.31-based. Shouldn't this be either what "stable"
> is currently (i.e. 2.6.32-based) or match up with Linus' tree (or
> the latest released version thereof)?

I keep forgetting to update it.  I think of it as a deprecated branch 
I'd like to get rid of, since the name is too vague.  In principle the 
name could be better used for something like "bleeding edge head", but I 
think changing its meaning like that would be way too much trouble, so 
just dropping it after migrating everything away from it is probably the 
best thing to do.

In the meantime, I'll make it the same as xen/stable-2.6.31.x, since 
that's more or less what it means.  (Likewise, xen/stable is tracking 
xen/stable-2.6.32.x at the moment).

I've also just started putting together a (pre-rc)2.6.36-based dom0 
branch which will become the development focus soon (leaving 2.6.32 
still supported but with backported changes, rather than the current 
flow of developing in .32 then forward-porting).

     J

  reply	other threads:[~2010-08-11  6:45 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-11  6:38 master branch of xen.git Jan Beulich
2010-08-11  6:45 ` Jeremy Fitzhardinge [this message]
2010-08-11  6:58   ` Jan Beulich
2010-08-13  0:46     ` Jeremy Fitzhardinge

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=4C6246F5.70309@goop.org \
    --to=jeremy@goop.org \
    --cc=JBeulich@novell.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.