From: Jeremy Fitzhardinge <jeremy@goop.org>
To: bderzhavets@yahoo.com
Cc: Ian Campbell <Ian.Campbell@eu.citrix.com>,
"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: Build vmlinuz-2.6.29-rc5-tip
Date: Tue, 17 Feb 2009 10:41:04 -0800 [thread overview]
Message-ID: <499B04C0.5070207@goop.org> (raw)
In-Reply-To: <647346.59661.qm@web56101.mail.re3.yahoo.com>
Boris Derzhavets wrote:
> It works fine.
> Thank you once again
>
> root@ServerXen331:/usr/src# mkdir linux.trees.git || exit -1
> root@ServerXen331:/usr/src# cd linux.trees.git
> root@ServerXen331:/usr/src/linux.trees.git# git init
> Initialized empty Git repository in /usr/src/linux.trees.git/.git/
> root@ServerXen331:/usr/src/linux.trees.git# git remote add linus
> git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux-2.6.git
> root@ServerXen331:/usr/src/linux.trees.git# git remote add tip
> git://git.kernel.org/pub/scm/linux/kernel/git/jeremy/xen.git
>
This is a fairly misleading name, and I think you'll just end up
confusing yourself. "linux-2.6-tip.git" is a different git tree that's
upstream to xen.git, but distinct from it. You'd be better off calling
this remote "xen".
J
next prev parent reply other threads:[~2009-02-17 18:41 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1234864748.30137.131.camel@zakaz.uk.xensource.com>
2009-02-17 10:06 ` How to build vmlinuz-2.6.29-rc5-tip ? Boris Derzhavets
2009-02-17 11:58 ` Build vmlinuz-2.6.29-rc5-tip Boris Derzhavets
2009-02-17 13:11 ` Pasi Kärkkäinen
2009-02-17 13:31 ` Boris Derzhavets
2009-02-17 13:57 ` Pasi Kärkkäinen
2009-02-17 18:40 ` Jeremy Fitzhardinge
2009-02-18 21:48 ` Pasi Kärkkäinen
2009-02-18 22:39 ` Jeremy Fitzhardinge
2009-02-19 7:21 ` Pasi Kärkkäinen
2009-02-19 3:13 ` Jeremy Fitzhardinge
2009-02-17 14:09 ` Marc - A. Dahlhaus [ Administration | Westermann GmbH ]
2009-02-18 15:49 ` Boris Derzhavets
2009-02-18 17:40 ` Boris Derzhavets
2009-02-18 18:53 ` Andrew Lyon
2009-02-18 19:16 ` Boris Derzhavets
2009-02-18 19:40 ` Boris Derzhavets
2009-02-18 20:04 ` Jeremy Fitzhardinge
2009-02-19 7:04 ` Boris Derzhavets
2009-02-19 17:30 ` Jeremy Fitzhardinge
2009-02-19 18:17 ` Boris Derzhavets
2009-02-20 9:04 ` Andrew Lyon
2009-02-20 9:36 ` Gerd Hoffmann
2009-02-20 12:24 ` Andrew Lyon
2009-02-21 12:40 ` Andrew Lyon
2009-02-21 15:53 ` Jeremy Fitzhardinge
2009-02-22 13:48 ` "xm dmesg" report for the most recent vmlinuz-2.6.29-rc5-tip Boris Derzhavets
2009-02-22 17:12 ` Jeremy Fitzhardinge
2009-02-22 17:27 ` Boris Derzhavets
2009-02-22 14:20 ` Build vmlinuz-2.6.29-rc5-tip Andrew Lyon
2009-02-22 15:10 ` Boris Derzhavets
2009-02-22 15:19 ` Andrew Lyon
2009-02-22 17:13 ` Boris Derzhavets
2009-02-23 16:32 ` Ian Jackson
2009-02-20 14:58 ` Jeremy Fitzhardinge
2009-02-20 15:39 ` Andrew Lyon
2009-02-20 19:44 ` Andrew Lyon
2009-02-20 19:59 ` Boris Derzhavets
2009-02-23 2:39 ` Stefano Stabellini
2009-02-23 10:19 ` Boris Derzhavets
2009-02-23 10:48 ` Boris Derzhavets
2009-02-21 9:01 ` Reproduced error when creating Intrepid HVM at Xen Unstable Dom0(vmlinuz-2.6.29-rc5-tip) Boris Derzhavets
2009-02-23 16:42 ` Ian Jackson
2009-02-23 18:04 ` Boris Derzhavets
2009-02-17 18:41 ` Jeremy Fitzhardinge [this message]
2009-02-18 6:36 ` Re: Build vmlinuz-2.6.29-rc5-tip 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=499B04C0.5070207@goop.org \
--to=jeremy@goop.org \
--cc=Ian.Campbell@eu.citrix.com \
--cc=bderzhavets@yahoo.com \
--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.