From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Jan Beulich" Subject: Re: Xen 4.2 TODO / Release Plan Date: Wed, 20 Jun 2012 17:06:50 +0100 Message-ID: <4FE2113A020000780008AE6D@nat28.tlf.novell.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> <20449.61581.396812.290324@mariner.uk.xensource.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <20449.61581.396812.290324@mariner.uk.xensource.com> Content-Disposition: inline List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Ian Jackson Cc: "xen-devel@lists.xen.org" , Ian Campbell , Stefano Stabellini List-Id: xen-devel@lists.xenproject.org >>> On 20.06.12 at 17:47, Ian Jackson wrote: > Jan Beulich writes ("Re: [Xen-devel] Xen 4.2 TODO / Release Plan"): >> 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. > > Certainly there is nothing automatic (people or computers) that fishes > changes to qemu upstream into -traditional. If you want something > committed to qemu-xen-traditional you'll have to say so. I'm not talking about anything automatic here. The need for pulling the change over was pointed out a number of times by both Stefano and me. Anyway - do you need a formal patch submission, or can you just pull out the one important and possibly one secondary commits? Jan