From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1KQOfP-0006ZO-S7 for qemu-devel@nongnu.org; Tue, 05 Aug 2008 11:41:43 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1KQOfO-0006Z0-1t for qemu-devel@nongnu.org; Tue, 05 Aug 2008 11:41:43 -0400 Received: from [199.232.76.173] (port=32819 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1KQOfN-0006Yx-Sb for qemu-devel@nongnu.org; Tue, 05 Aug 2008 11:41:41 -0400 Received: from smtp.eu.citrix.com ([62.200.22.115]:38991) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1KQOfN-0002eH-KA for qemu-devel@nongnu.org; Tue, 05 Aug 2008 11:41:41 -0400 Date: Tue, 5 Aug 2008 16:41:40 +0100 From: Samuel Thibault Subject: Re: [Qemu-devel] [PATCH 0/7] merge some xen bits into qemu Message-ID: <20080805154140.GV4478@implementation.uk.xensource.com> References: <1217865045-10722-1-git-send-email-kraxel@redhat.com> <48973F8E.8080109@codemonkey.ws> <20080805104630.GM4478@implementation.uk.xensource.com> <489835A3.6030804@redhat.com> <20080805112935.GO4478@implementation.uk.xensource.com> <48985336.2020709@redhat.com> <20080805150328.GT4478@implementation.uk.xensource.com> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <20080805150328.GT4478@implementation.uk.xensource.com> Reply-To: qemu-devel@nongnu.org List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Gerd Hoffmann , Anthony Liguori , qemu-devel@nongnu.org, xen-devel@lists.xensource.com, Ian Jackson Samuel Thibault, le Tue 05 Aug 2008 16:03:28 +0100, a écrit : > Gerd Hoffmann, le Tue 05 Aug 2008 15:18:46 +0200, a écrit : > > Samuel Thibault wrote: > > > Then it'd probably be good to push that upstream Xen. > > > > I'm cross-posting the patches to xen-devel for a reason. > > Well, cross-posting qemu patches to xen-devel is not the same as posting > xen patches to xen-devel... Just to explain a bit more, now that I have read the patches a bit: what is there is somehow far from the xen unstable tree, at least because of the backend driver core, and because of other 'details' (renaming, moving). I doubt Ian will be happy to have to make the effort to merge that in his tree and I guess he will probably just drop everything and keep the xen-unstable version. Samuel