From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ian Campbell Subject: Re: Xen 4.2 TODO / Release Plan Date: Wed, 20 Jun 2012 16:50:07 +0100 Message-ID: <1340207407.4906.77.camel@zakaz.uk.xensource.com> References: <1339506046.24104.30.camel@zakaz.uk.xensource.com> <4FD766E2020000780008974F@nat28.tlf.novell.com> <1339509935.24104.66.camel@zakaz.uk.xensource.com> <1340205929.4906.66.camel@zakaz.uk.xensource.com> <4FE20B23020000780008AE16@nat28.tlf.novell.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <4FE20B23020000780008AE16@nat28.tlf.novell.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Jan Beulich Cc: "xen-devel@lists.xen.org" , Ian Jackson , Stefano Stabellini List-Id: xen-devel@lists.xenproject.org On Wed, 2012-06-20 at 16:40 +0100, Jan Beulich wrote: > > That thread also references > > <4FABFCF40200007800082CE0@nat28.tlf.novell.com> as something which > > should be applied to the trad tree too. Has anyone tested that combo? > > > > I can see how Ian missed this -- it very much looked like those two > > patches were for qemu-upstream only to me (from the subject, cc line etc > > etc). > > I didn't think that I needed to formally submit patches that were > requested to be ported over to -traditional when they already > went into upstream qemu. If I'm wrong with this, then please let > me know and I'll submit both patches asap. This is really for Ian J to say but IMHO the two code bases have diverged enough that blindly pulling from upstream -> traditional is not a good idea, so at the least the change needs to be tested in that context. Even if we were happy to just pull things in then the mail needs to note somewhere which tree(s) the patch should be applied to. Ian.