All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dick Davies <rasputnik@hellooperator.net>
To: Ian Pratt <Ian.Pratt@cl.cam.ac.uk>
Cc: Xen Devel <xen-devel@lists.sourceforge.net>
Subject: Re: Xen 2.0 beta
Date: Tue, 31 Aug 2004 16:59:46 +0100	[thread overview]
Message-ID: <20040831155946.GA10705@lb.tenfour> (raw)
In-Reply-To: <E1C0pN4-0007pT-00@mta1.cl.cam.ac.uk>

* Ian Pratt <Ian.Pratt@cl.cam.ac.uk> [0840 23:40]:

> To clone the proto 2.0 tree use "bk clone bk://xen.bkbits.net/xen-2.0.bk"

> NB: We've named the repository 'xen' rather than 'xeno' as the
> latter name no longer makes sense now that the XenoServer project
> now lives in a different repository. 

Can you update the user guide, it still refers to xeno:

http://www.cl.cam.ac.uk/Research/SRG/netos/xen/readmes/user/user.html#SECTION02241000000000000000


--------8<-----------------

Using Bitkeeper

The public master BK repository for the 2.0 release lives at:
bk://xen.bkbits.net/xen-2.0.bk. You can use Bitkeeper to download it and keep it updated with the latest features and fixes.

Change to the directory in which you want to put the source code, then run:

# bk clone bk://xen.bkbits.net/xeno-2.0.bk

Under your current directory, a new directory named `xeno-2.0.bk' has been created, which contains all the source code for the Xen hypervisor and the Xen tools. The directory also contains `sparse' Linux source trees, containing only the files that differ between XenLinux and standard Linux.

Once you have cloned the repository, you can update to the newest changes to the repository by running:

# cd xeno-2.0.bk # to change into the local repository
# bk pull        # to update the repository

--------8<-----------------
 
-- 
The sooner you make your first 5000 mistakes, the sooner you will be
able to correct them.
		-- Nicolaides
Rasputin :: Jack of All Trades - Master of Nuns


-------------------------------------------------------
This SF.Net email is sponsored by BEA Weblogic Workshop
FREE Java Enterprise J2EE developer tools!
Get your free copy of BEA WebLogic Workshop 8.1 today.
http://ads.osdn.com/?ad_id=5047&alloc_id=10808&op=click

  parent reply	other threads:[~2004-08-31 15:59 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-27 22:38 Xen 2.0 beta Ian Pratt
2004-08-27 22:57 ` ron minnich
2004-08-27 23:01   ` Ian Pratt
2004-08-28  2:46     ` ron minnich
2004-08-28  4:35 ` James Harper
2004-08-28  6:35   ` Ian Pratt
2004-09-14 20:17     ` Rob Gardner
2004-09-14 20:35       ` Steven Hand
2004-09-14 21:25         ` Rob Gardner
2004-09-14 21:57           ` Keir Fraser
2004-09-14 22:08             ` Rob Gardner
2004-09-14 22:22               ` Keir Fraser
2004-09-14 22:00           ` Steven Hand
2004-09-14 22:09             ` Rob Gardner
2004-09-14 20:35       ` Kip Macy
2004-08-28  9:12 ` James Harper
2004-08-28  9:28   ` Christian Limpach
2004-08-28 12:00     ` James Harper
2004-08-29  1:23 ` James Harper
2004-08-29  1:45   ` Mike Brady
2004-08-29  1:50     ` Keir Fraser
2004-08-29  1:52     ` Mark Williamson
2004-08-29  2:09       ` James Harper
2004-08-29  2:11       ` Mike Brady
2004-08-29  2:11   ` James Harper
2004-08-31 15:59 ` Dick Davies [this message]
2004-08-31 16:08   ` Mark Williamson
2004-08-31 16:21   ` Steven Hand

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=20040831155946.GA10705@lb.tenfour \
    --to=rasputnik@hellooperator.net \
    --cc=Ian.Pratt@cl.cam.ac.uk \
    --cc=xen-devel@lists.sourceforge.net \
    /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.