All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Bruce Edge <bruce.edge@gmail.com>
Cc: xen-devel@lists.xensource.com,
	Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Subject: Re: pvops kernel branches - 2.6.36 options, stable/next/etc?
Date: Mon, 08 Nov 2010 11:14:36 -0800	[thread overview]
Message-ID: <4CD84C1C.3090703@goop.org> (raw)
In-Reply-To: <AANLkTi=AZw8_XJbO=fMD5nfp6Mp9QvWaxRPE8Z7nzq42@mail.gmail.com>

On 11/08/2010 10:19 AM, Bruce Edge wrote:
> Is there now or will there be a 2.6.36 stable branch, or is the only
> option for this version the next-2.6.36 branch?

No.  xen/next-2.6.36 doesn't exist any more, and it never really
contained anything useful.  xen/next-2.6.37, however, is closely
tracking upstream and I hope will reach functional parity with the
2.6.32-based branches.

>
> In the past Jeremy has posted details on the state and forward goals
> for the major consolidation branches.
> I haven't seen any such details regarding the .36/.37 branches.
> Does any one know what the plans are?

I'll post something the next week or so when we work out what needs to
happen with .37 to get it up to speed.

>
> We've been hanging off of Konrad's  stable/xen-pcifront-0.8.2 branch
> with good results. I'm wondering what our options are now with the
> recent merge storm.

That has been merged into mainline Linux.

    J

  reply	other threads:[~2010-11-08 19:14 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-08 18:19 pvops kernel branches - 2.6.36 options, stable/next/etc? Bruce Edge
2010-11-08 19:14 ` Jeremy Fitzhardinge [this message]
2010-11-09 10:26   ` Thomas Goirand
2010-11-10 18:13     ` Jeremy Fitzhardinge
2010-11-12  7:43       ` Boris Derzhavets
2010-11-09 11:20   ` Boris Derzhavets
2010-11-09 15:00     ` Konrad Rzeszutek Wilk
2010-11-09 16:27       ` Boris Derzhavets
2010-11-10 18:17   ` Bruce Edge
2010-11-10 18:27     ` Jeremy Fitzhardinge
2010-11-10 19:43     ` Konrad Rzeszutek Wilk
2010-11-10 20:04       ` Bruce Edge
2010-11-11 14:58       ` Bruce Edge
2010-11-11 16:25         ` Konrad Rzeszutek Wilk
2010-11-11 16:48           ` Bruce Edge
2010-11-11 16:55             ` Konrad Rzeszutek Wilk
2010-11-11 18:09             ` Boris Derzhavets
2010-11-11 18:32               ` Bruce Edge
2010-11-11 18:50                 ` Boris Derzhavets
2010-11-11 20:03                 ` Boris Derzhavets
2010-11-11 20:20                   ` Bruce Edge
2010-11-11 21:11                     ` Konrad Rzeszutek Wilk
2010-11-11 22:06                       ` Bruce Edge
2010-11-11 22:25                         ` Konrad Rzeszutek Wilk

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=4CD84C1C.3090703@goop.org \
    --to=jeremy@goop.org \
    --cc=bruce.edge@gmail.com \
    --cc=konrad.wilk@oracle.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.