From mboxrd@z Thu Jan 1 00:00:00 1970 From: Konrad Rzeszutek Wilk Subject: Re: Re: make xen/stable-2.6.32.x pvops branch the default? Date: Tue, 8 Jun 2010 12:15:45 -0400 Message-ID: <20100608161545.GB4900@phenom.dumpdata.com> References: <20100608111501.GP17817@reaktio.net> <4C0E667F.2040306@goop.org> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Return-path: Content-Disposition: inline In-Reply-To: <4C0E667F.2040306@goop.org> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Jeremy Fitzhardinge Cc: xen-devel@lists.xensource.com, Keir Fraser List-Id: xen-devel@lists.xenproject.org On Tue, Jun 08, 2010 at 08:49:19AM -0700, Jeremy Fitzhardinge wrote: > On 06/08/2010 04:15 AM, Pasi K=E4rkk=E4inen wrote: > > Should we switch xen/stable-2.6.32.x to be the default branch in xen-= unstable?=20 > > And possibly in xen-4.0-testing.hg aswell?=20 > > =20 >=20 > Yes, I was just thinking that. On top of that, what about that udev(new version) race condition? I think James and Bastian both provided a patch - does it make sense to merge it in both branches (.31 and .32)?