bitkeeper revision 1.470.1.1 (3f783cec2WipJHPjRa8BMX27L9ph6A)

1.0rc1 -> 1.0

diff --git a/README.CD b/README.CD
index d4ff7e2961953fa4176f4c88e7df04707c868e2c..4cb68f9675ee45e8f7aa5d72d38b3c40acf64c71 100644 (file)
--- a/README.CD
+++ b/README.CD
@@ -7,9 +7,9 @@
                                                    
 #############################
 
- XenDemoCD 1.0 rc1 
+ XenDemoCD 1.0 
  University of Cambridge Computer Laboratory
- 18 Sep 2003
+ 29 Sep 2003
 
  http://www.cl.cam.ac.uk/netos/xen
 
@@ -429,7 +429,7 @@ figuring out what's happened.  Debug a XenoLinux image just as you
 would any other Linux kernel.
 
 We supply a handy debug terminal program which you can find in
-/usr/local/src/xen-1.0rc1/xeno.bk/tools/misc/miniterm/
+/usr/local/src/xen-1.0/xeno.bk/tools/misc/miniterm/
 This should be built and executed on another machine that is connected
 via a null modem cable. Documentation is included.
 Alternatively, telnet can be used in 'char mode' if the Xen machine is

diff --git a/xen/Makefile b/xen/Makefile
index b24ad891745776e3fda5dcbd0d0f20a10c6af5cb..bc939340ea8a296c77b9fcdbe51f7a3354e0433c 100644 (file)
--- a/xen/Makefile
+++ b/xen/Makefile
@@ -3,7 +3,7 @@
 # All other places this is stored (eg. compile.h) should be autogenerated.
 export XEN_VERSION       = 1
 export XEN_SUBVERSION    = 0
-export XEN_EXTRAVERSION  = "-rc1"
+export XEN_EXTRAVERSION  = ""
 
 export BASEDIR          := $(shell pwd)