WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Xen

xen-devel

[Top] [All Lists]

[Xen-devel] Re: [PATCH 00 of 10] blkfront pvops updates

To: Jeremy Fitzhardinge <jeremy@xxxxxxxx>
Subject: [Xen-devel] Re: [PATCH 00 of 10] blkfront pvops updates
From: Daniel Stodden <daniel.stodden@xxxxxxxxxx>
Date: 2010年4月29日 16:05:46 -0700
Cc: ksrinivasan <ksrinivasan@xxxxxxxxxx>, Xen <xen-devel@xxxxxxxxxxxxxxxxxxx>, Jan Beulich <JBeulich@xxxxxxxxxx>
Delivery-date: 2010年4月29日 16:07:12 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <4BD9FBC9.4010100@xxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <patchbomb.1272507577@xxxxxxxxxxxxxxxxxxxxxxx> <4BD9E2EE.5060402@xxxxxxxx> <1272571912.25447.11.camel@xxxxxxxxxxxxxxxxxxxxxxx> <1272574715.25447.34.camel@xxxxxxxxxxxxxxxxxxxxxxx> <4BD9F5DC.4040208@xxxxxxxx> <1272576531.25447.39.camel@xxxxxxxxxxxxxxxxxxxxxxx> <4BD9FBC9.4010100@xxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
On Thu, 2010年04月29日 at 17:36 -0400, Jeremy Fitzhardinge wrote:
> On 04/29/2010 02:28 PM, Daniel Stodden wrote:
> > So I'm probably building the wrong tree by default.
> >
> > I used to make linux-2.6-pvops when starting to work.
> > Which checks out xen/master.
> >
> > How does this relate?
> > 
>
> xen/master is an alias for xen/stable-2.6.31.x at the moment. I just
> submitted a patch to make this switchover explicit, and will move it to
> 2.6.32 soon.
Okay, so xen/master rather defaults to some stable tree.
If xen/frontend is the topic branch, people ideally prepare patches per
topic, and trunk is rather xen/next, then the thing I still don't follow
is than xen/frontend hasn't been merged since
* commit 8800a1de3df00fa994f72ad0d7c1eda9b5a0b514
| Author: Paolo Bonzini <pbonzini@xxxxxxxxxx>
| Date: Wed Jul 8 12:27:37 2009 +0200
Why would I want to build a kernel derived from last July's state? Or,
put differently: Is it okay to merge these topic branches before
anything else?
Daniel
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
<Prev in Thread] Current Thread [Next in Thread>
Previous by Date: [Xen-devel] Dom0 restartability , Subbiah Kandasamy (skandasa)
Next by Date: RE: [Xen-devel] Re: drbd: and hvm , James Harper
Previous by Thread: [Xen-devel] Re: [PATCH 00 of 10] blkfront pvops updates , Jeremy Fitzhardinge
Next by Thread: [Xen-devel] Re: [PATCH 00 of 10] blkfront pvops updates , Jeremy Fitzhardinge
Indexes: [Date] [Thread] [Top] [All Lists]

Copyright ©, Citrix Systems Inc. All rights reserved. Legal and Privacy
Citrix This site is hosted by Citrix

AltStyle によって変換されたページ (->オリジナル) /