From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1KQrIz-0005K9-CR
	for qemu-devel@nongnu.org; Wed, 06 Aug 2008 18:16:29 -0400
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1KQrIx-0005JX-NS
	for qemu-devel@nongnu.org; Wed, 06 Aug 2008 18:16:28 -0400
Received: from [199.232.76.173] (port=45500 helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1KQrIx-0005JU-J6
	for qemu-devel@nongnu.org; Wed, 06 Aug 2008 18:16:27 -0400
Received: from mtaout01-winn.ispmail.ntl.com ([81.103.221.47]:30743)
	by monty-python.gnu.org with esmtp (Exim 4.60)
	(envelope-from <samuel.thibault@labri.fr>) id 1KQrIx-0003Vt-EX
	for qemu-devel@nongnu.org; Wed, 06 Aug 2008 18:16:27 -0400
Date: Wed, 6 Aug 2008 23:16:23 +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: <20080806221623.GF4486@implementation>
References: <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>
	<4899C4CB.2020105@redhat.com>
	<20080806154713.GQ4448@implementation.uk.xensource.com>
	<489A2144.20004@redhat.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <489A2144.20004@redhat.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>
Cc: xen-devel@lists.xensource.com, Ian Jackson <Ian.Jackson@eu.citrix.com>, Markus Armbruster <armbru@redhat.com>, qemu-devel@nongnu.org

Gerd Hoffmann, le Thu 07 Aug 2008 00:10:12 +0200, a écrit :
> Samuel Thibault wrote:
> > Gerd Hoffmann, le Wed 06 Aug 2008 17:35:39 +0200, a écrit :
> >>> AGAIN, THERE IS THE IAN JACKSON TREE.
> >>>
> >>> Thanks for reading.
> >> I get build failures when patching THE IAN JACKSON TREE due to THE IAN
> >> JACKSON TREE lagging behind upstream.
> > 
> > You didn't mention that. "lagging" a few months indeed, while merging
> > stuff.  And because xen 4.0 is about to be released, but it will
> > probably catch up soon.
> 
> Well, for 4.0.x you probably have to branch off anyway,

When 4.0 gets released, yes.

> so the release shouldn't stop catching up with upstream.

The way Xen has been working up to now is to branch the trunk just after
the release, not before.

> > Anyway that's not a reason for not using it, I
> > guess the build failures can be fixed more easily than redoing Ian's
> > work.
> 
> I'm using upstream qemu for development, and I'm not going to change that.

No problem.

> I can adapt the patches for the xen tree.

That's what I'm asking you from the start of the thread, I guess my
english is not so clear.

> Having the xen tree *not* lagging behind would be *very* helpful for
> keeping the trees and patches in sync.

Sure, it just happens that it couldn't be done before we get Ian's tree
working.  Once the 4.0 release is done we can tighten the gap.  And
things that shouldn't be only in Ian's tree (e.g. the enhanced serial
support) are being pushed already.

Samuel