All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ian Campbell <Ian.Campbell@citrix.com>
To: "bderzhavets@yahoo.com" <bderzhavets@yahoo.com>
Cc: Jeremy Fitzhardinge <jeremy@goop.org>,
	"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: How to build vmlinuz-2.6.29-rc5-tip ?
Date: Tue, 17 Feb 2009 08:28:39 +0000	[thread overview]
Message-ID: <1234859319.26552.28.camel@localhost.localdomain> (raw)
In-Reply-To: <162938.82174.qm@web56103.mail.re3.yahoo.com>

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.

  reply	other threads:[~2009-02-17  8:28 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-16 21:54 Console output with pv_ops kernel jonr
2009-02-16 22:53 ` Jeremy Fitzhardinge
2009-02-17  5:14   ` How to build vmlinuz-2.6.29-rc5-tip ? Boris Derzhavets
2009-02-17  8:15     ` Boris Derzhavets
2009-02-17  8:28       ` Ian Campbell [this message]
2009-02-17  9:40         ` Boris Derzhavets
2009-02-17 10:00           ` M A Young
2009-02-17 11:59             ` Boris Derzhavets
     [not found] <1234864748.30137.131.camel@zakaz.uk.xensource.com>
2009-02-17 10:06 ` Boris Derzhavets

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1234859319.26552.28.camel@localhost.localdomain \
    --to=ian.campbell@citrix.com \
    --cc=bderzhavets@yahoo.com \
    --cc=jeremy@goop.org \
    --cc=xen-devel@lists.xensource.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.