All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gerd Hoffmann <kraxel@redhat.com>
To: echo@echoreply.us
Cc: Xen-devel <xen-devel@lists.xensource.com>,
	Andrew Lyon <andrew.lyon@gmail.com>,
	Keir Fraser <keir.fraser@eu.citrix.com>
Subject: Re: Xen dom0 Kernel Patches
Date: Thu, 04 Jun 2009 08:59:19 +0200	[thread overview]
Message-ID: <4A2770C7.2020605@redhat.com> (raw)
In-Reply-To: <1244087028.7176.17.camel@localhost.localdomain>

On 06/04/09 05:43, Tim Post wrote:
> On Wed, 2009-06-03 at 22:31 +0100, Keir Fraser wrote:
>
>> Yes, it doesn't have to be all pushed upstream for it to be used. It's just
>> a question of how big the out-of-upstream patchset is that Jeremy has to
>> manage. And actually there's maintenance work even with the upstreamed
>> patches, of course. But none of that directly matters for consumers of
>> Jeremy's tree.
>
> No, of course it doesn't. The problem is, Jeremy's tree is very much a
> moving target as he works to produce patches that upstream will accept.

Well, that might be fixable without too much effort.  Maybe jeremy could 
simply branch off a stable branch for 2.6.30 before rebasing to 
2.6.31-rc1?  Just to have something people can pull which is not based 
on some -rc bleeding edge kernel?  That branch wouldn't get updates, 
except maybe for cherry-picked bugfixes, maybe also 2.6.30.x stable 
patches if they apply cleanly.  Development would still happen in the 
xen-next + xen-master branches of course.

cheers,
   Gerd

  reply	other threads:[~2009-06-04  6:59 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-03 18:49 Xen dom0 Kernel Patches Andrew Lyon
2009-06-03 19:35 ` Pasi Kärkkäinen
2009-06-03 20:36   ` Andrew Lyon
2009-06-04 15:08   ` Ian Pratt
2009-06-03 21:24 ` Gerd Hoffmann
2009-06-03 21:31   ` Keir Fraser
2009-06-04  3:43     ` Tim Post
2009-06-04  6:59       ` Gerd Hoffmann [this message]
2009-06-04 14:36         ` Tim Post
  -- strict thread matches above, loose matches on Subject: below --
2009-06-04 17:55 Boris Derzhavets
2009-06-04 18:18 ` 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=4A2770C7.2020605@redhat.com \
    --to=kraxel@redhat.com \
    --cc=andrew.lyon@gmail.com \
    --cc=echo@echoreply.us \
    --cc=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.