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 
 
Home Products Support Community News
 
   
 

xen-devel

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

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