From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1KQjEK-0003QZ-G8 for qemu-devel@nongnu.org; Wed, 06 Aug 2008 09:39:08 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1KQjEH-0003Mp-Mx for qemu-devel@nongnu.org; Wed, 06 Aug 2008 09:39:07 -0400 Received: from [199.232.76.173] (port=37276 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1KQjEH-0003ML-9s for qemu-devel@nongnu.org; Wed, 06 Aug 2008 09:39:05 -0400 Received: from smtp.ctxuk.citrix.com ([62.200.22.115]:8575 helo=SMTP.EU.CITRIX.COM) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1KQjEG-00046x-VI for qemu-devel@nongnu.org; Wed, 06 Aug 2008 09:39:05 -0400 Date: Wed, 6 Aug 2008 14:39:03 +0100 From: Samuel Thibault Subject: Re: [Qemu-devel] [PATCH 0/7] merge some xen bits into qemu Message-ID: <20080806133903.GH4448@implementation.uk.xensource.com> References: <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> <20080805154140.GV4478@implementation.uk.xensource.com> <48997981.1030703@redhat.com> <20080806102338.GA4448@implementation.uk.xensource.com> <4899A617.6040506@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <4899A617.6040506@redhat.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 Cc: xen-devel@lists.xensource.com, Ian Jackson , qemu-devel@nongnu.org Gerd Hoffmann, le Wed 06 Aug 2008 15:24:39 +0200, a écrit : > > You forgot the _test_ stage. You are basically asking us to replace our > > well-tested implementation with your implementation, that's quite a > > move. > > Sure, and more will follow. But by having it merged into just upstream qemu you won't magically get Xen people actually test it, so it would be mostly dead code. > Pretty much like upstreaming the xen support into the linux kernel. There's a big difference here. The upstream linux kernel merge won't be merged back to the linux-2.6.18 tree. And people do test upstream xen support. Samuel