All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeremy Fitzhardinge <jeremy@goop.org>
To: bderzhavets@yahoo.com
Cc: jonr@destar.net, xen-devel@lists.xensource.com
Subject: Re: xend start error
Date: Wed, 18 Feb 2009 12:01:55 -0800	[thread overview]
Message-ID: <499C6933.4090104@goop.org> (raw)
In-Reply-To: <666471.31452.qm@web56104.mail.re3.yahoo.com>

Boris Derzhavets wrote:
> Jon,
>
> I just finished testing  Marc - A. Dahlhaus's  procedure:-
> ********************************************************************
> with git >= v1.5 you can get to the right branch even simpler with:
> ********************************************************************
> # 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/xen/dom0/hackery -b xen/dom0/hackery
>
> To update:
> git pull
>

Thanks for this.  I'm updating the wiki page at 
http://wiki.xensource.com/xenwiki/XenParavirtOps, and I'll include this 
as a nice simple way to get started.

    J

  parent reply	other threads:[~2009-02-18 20:01 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-17 21:33 xend start error jonr
2009-02-17 23:06 ` Jeremy Fitzhardinge
2009-02-17 23:27   ` jonr
2009-02-18  7:01     ` Boris Derzhavets
2009-02-18  8:00       ` Jeremy Fitzhardinge
2009-02-18  8:01         ` Boris Derzhavets
2009-02-18  8:26           ` Boris Derzhavets
2009-02-18  8:30             ` Jeremy Fitzhardinge
2009-02-18  9:04               ` Boris Derzhavets
2009-02-18 17:47       ` jonr
2009-02-18 18:03         ` Boris Derzhavets
2009-02-18 18:49           ` jonr
2009-02-18 19:23             ` Boris Derzhavets
2009-02-18 20:01           ` Jeremy Fitzhardinge [this message]
  -- strict thread matches above, loose matches on Subject: below --
2005-04-14 12:50 Paul Larson
2005-04-14 14:52 ` Paul Larson
2005-04-14 16:05   ` Adam Heath

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=499C6933.4090104@goop.org \
    --to=jeremy@goop.org \
    --cc=bderzhavets@yahoo.com \
    --cc=jonr@destar.net \
    --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.