From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jeremy Fitzhardinge Subject: Re: xen.git branch reorg Date: Thu, 23 Apr 2009 11:32:14 -0700 Message-ID: <49F0B42E.2040904@goop.org> References: <49F0A797.1050402@goop.org> <20090423182451.GV24960@edu.joroinen.fi> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: quoted-printable Return-path: In-Reply-To: <20090423182451.GV24960@edu.joroinen.fi> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: =?ISO-8859-1?Q?Pasi_K=E4rkk=E4inen?= Cc: Xen-devel List-Id: xen-devel@lists.xenproject.org Pasi K=E4rkk=E4inen wrote: > I'll try upgrading from dom0/hackery to xen-tip/next and see how it wor= ks > for me.=20 > =20 Thanks. > Btw how does dom0 upstreaming look at the moment? Ingo sent pull reques= t > about some changes, and those got merged, but how about the rest?=20 Ingo basically ignored all the Xen changes in the leadup to the merge=20 window, then stomped on my attempt to get them merged with Linus, which=20 was all pretty annoying. It had the doubly-irritating side-effect of=20 casting doubt over the controversy-free domU changes, so they didn't get=20 merged in the merge window either; by the time Ingo got around to OKing=20 them, the window had closed. So all that got merged in the end was the=20 must-have bug fixes. Linus isn't going to pull any more major functionality changes in the=20 -rc kernels, and certainly isn't going to make an exception for Xen. So=20 we're stuck with waiting for the .31 merge window. J