From: Jeremy Fitzhardinge <jeremy@goop.org>
To: bderzhavets@yahoo.com
Cc: "H. Peter Anvin" <hpa@zytor.com>,
Xen-devel <xen-devel@lists.xensource.com>,
the arch/x86 maintainers <x86@kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [Xen-devel] [PATCH] xen: core dom0 support
Date: Fri, 27 Feb 2009 22:23:04 -0800 [thread overview]
Message-ID: <49A8D848.3000907@goop.org> (raw)
In-Reply-To: <185173.37814.qm@web56102.mail.re3.yahoo.com>
Boris Derzhavets wrote:
>
> Does it mean that Wiki Page should look now as ?
> ----------------------------------------------------------------------------------------------------------------------
> git clone
> git://git.kernel.org/pub/scm/linux/kernel/git/jeremy/xen.git
> linux-2.6-xen
> cd linux-2.6-xen
> git checkout origin/push/xen/dom0/core -b push/xen/dom0/core
>
No. That branch is far from complete; the push/* branches are just for
upstreaming things to the kernel, and are not independently useful.
xen/dom0/hackery continues to be the best place to get complete (as far
as it goes) dom0 support.
J
parent reply other threads:[~2009-02-28 6:23 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <185173.37814.qm@web56102.mail.re3.yahoo.com>]
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=49A8D848.3000907@goop.org \
--to=jeremy@goop.org \
--cc=bderzhavets@yahoo.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=x86@kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox