From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1KQrDh-0001Ip-Mx
	for qemu-devel@nongnu.org; Wed, 06 Aug 2008 18:11:01 -0400
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1KQrDf-0001Hv-Sv
	for qemu-devel@nongnu.org; Wed, 06 Aug 2008 18:11:01 -0400
Received: from [199.232.76.173] (port=49257 helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1KQrDf-0001Hl-M3
	for qemu-devel@nongnu.org; Wed, 06 Aug 2008 18:10:59 -0400
Received: from mtaout01-winn.ispmail.ntl.com ([81.103.221.47]:29335)
	by monty-python.gnu.org with esmtp (Exim 4.60)
	(envelope-from <samuel.thibault@labri.fr>) id 1KQrDf-0002yu-NJ
	for qemu-devel@nongnu.org; Wed, 06 Aug 2008 18:10:59 -0400
Date: Wed, 6 Aug 2008 23:10:47 +0100
From: Samuel Thibault <samuel.thibault@eu.citrix.com>
Subject: Re: [Xen-devel] Re: [Qemu-devel] [PATCH 0/7] merge some xen bits into
	qemu
Message-ID: <20080806221047.GE4486@implementation>
References: <20080805150328.GT4478@implementation.uk.xensource.com>
	<20080805154140.GV4478@implementation.uk.xensource.com>
	<48997981.1030703@redhat.com>
	<20080806102338.GA4448@implementation.uk.xensource.com>
	<m37iauxqii.fsf@crossbow.pond.sub.org>
	<20080806125055.GG4448@implementation.uk.xensource.com>
	<4899AD19.8060606@redhat.com>
	<20080806140132.GL4448@implementation.uk.xensource.com>
	<4899B06F.2090101@redhat.com>
	<20080806142526.GN4448@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: <20080806142526.GN4448@implementation.uk.xensource.com>
Reply-To: qemu-devel@nongnu.org
List-Id: qemu-devel.nongnu.org
List-Unsubscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/pipermail/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: Gerd Hoffmann <kraxel@redhat.com>, Markus Armbruster <armbru@redhat.com>, Anthony Liguori <anthony@codemonkey.ws>, qemu-devel@nongnu.org, xen-devel@lists.xensource.com, Ian Jackson <Ian.Jackson@eu.citrix.com>

Samuel Thibault, le Wed 06 Aug 2008 15:25:26 +0100, a écrit :
> Pushing the cleaning changes to Xen first can be done and would entail
> much easier to tackle breakage, and the merge back from qemu would then
> be trivial, why not doing so?

You didn't answer that part.  Really, my only concern is about having
things tested.  Isn't it possible for instance to just merge the backend
core (and console/xenfb updates) in Ian's tree first for a start?  As
Markus and I said, it looked sane.  Then you can push your code to qemu,
I guess that could be fine, as you said xen will not need to use e.g.
the block and net backends.

Samuel