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

Re: [Xen-devel] How to build vmlinuz-2.6.29-rc5-tip ?

To: "bderzhavets@xxxxxxxxx" <bderzhavets@xxxxxxxxx>
Subject: Re: [Xen-devel] How to build vmlinuz-2.6.29-rc5-tip ?
From: Ian Campbell <Ian.Campbell@xxxxxxxxxx>
Date: Tue, 17 Feb 2009 08:28:39 +0000
Cc: Jeremy Fitzhardinge <jeremy@xxxxxxxx>, "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Tue, 17 Feb 2009 00:29:12 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <162938.82174.qm@xxxxxxxxxxxxxxxxxxxxxxxxxxx>
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>
Organization: Citrix Systems, Inc.
References: <162938.82174.qm@xxxxxxxxxxxxxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
On Tue, 2009-02-17 at 03:15 -0500, Boris Derzhavets wrote:
> 
> root@ServerXen331:/usr/src/linux.trees.git# git checkout -b tip-latest
> tip/master
> warning: You appear to be on a branch yet to be born.
> warning: Forcing checkout of tip/master.
> Checking out files: 100% (26687/26687), done.
> Branch tip-latest set up to track remote branch
> refs/remotes/tip/master.
> Switched to a new branch "tip-latest"
> 
> 
> "make menuconfig" still  doesn't show options for Xen Dom0 support.
> 

In Jeremy's announcement of the git tree he said:

> 
> If you want to get started, either xen/dom0/hackery or xen/master are 
> the places to start;
> 
> xen/dom0/hackery
>     Master dom0 branch.  This is all the interesting dom0-related topic
>     branches merged together, and is a superset of xen/master.
> xen/master
>     Master domU branch, with everything interesting merged in.  This is
>     likely to be more stable and closer to upstream than dom0/hackery

So I think you want the xen/dom0/hackery branch which would become
tip/xen/dom0/hackery in your repo (and xen/master=>tip/xen/master not
tip/master).

Ian.


_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel