diff --git a/README-CVS b/README-GIT
similarity index 91%
rename from README-CVS
rename to README-GIT
index f81ddbb8e6df32f59b9978307561f5720b02e3b0..b00437c83951c7ba1d9960645eb85be9b2f35e3a 100644
--- a/README-CVS
+++ b/README-GIT
@@ -1,21 +1,21 @@
 
-HOW TO BUILD PIKE FROM CVS
+HOW TO BUILD PIKE FROM GIT
 
 If you like to live at the bleeding edge you can download Pike from
-CVS with all the latest additions from the developers.  There are two
+git with all the latest additions from the developers.  There are two
 major branches in the archive, the latest stable branch and latest
 development branch.  Stable versions have an even minor version
 number, i.e. 7.0.x, 7.2.x, 7.4.x, whereas the development branches
 have an odd minor version.
 
-Keep in mind that the CVS versions are under heavy development and
+Keep in mind that the git versions are under heavy development and
 have not been tested nearly as well as the offcial releases.  You use
 the code AT YOUR OWN RISK.
 
 
 DEPENDENCIES
 
-Building from CVS requires the same tools as building from a source
+Building from git requires the same tools as building from a source
 distribution (gnu m4, bison and a C compiler, suggested also GNU make
 and libz), and then some.  In addition to thosee requirements, you
 need a working Pike, autoconf and gcc (to generate the dependency
@@ -26,24 +26,17 @@ Not all autoconf versions meet Pike's requirements.  Autoconf version
 are known to not work.
 
 
-CHECKING OUT PIKE FROM CVS
+CHECKING OUT PIKE FROM GIT
 
-1. Get a recent version of cvs.
+1. Get a recent version of git (1.7.2 or later).
 
-2. Login to the CVS server:
+2. Clone the git repository with
 
-         cvs -d :pserver:anon@cvs.roxen.com:/cvs login
+         git clone git://pike-git.lysator.liu.se/pike.git
 
-   Just hit enter on the password prompt.
-
-3. Check out the source:
-
-         cvs -z3 -d :pserver:anon@cvs.roxen.com:/cvs co Pike/7.8
-
-   substitute 7.8 for whatever version you want to get.
 
 The top-level makefile (in this directory, not the src directory) has
-all the magic you need to build Pike directly from CVS.  Just type
+all the magic you need to build Pike directly from git.  Just type
 'make'.  It is preferable to build from the toplevel since it avoids
 contaminating the source tree with object files and other generated
 files.
@@ -71,7 +64,7 @@ source              Prepare the source tree for compilation without
                     the need for a preexisting installed Pike.
 force_autoconfig    Force a build of the configure scripts.  This is
                     useful e.g. if a new module directory is added in
-                    the CVS.
+                    the git.
 force_configure     Force configure to be run (recursively).
 reconfigure         Remove the cached results from previous configure
                     runs and rerun configure recursively. If you have
@@ -90,12 +83,12 @@ force_dump_modules  Force all Pike modules to be redumped, not just
                     those whose source files have changed.
 snapshot            Create a snapshot export tarball.
 export              Create a source dist and bump up the build number
-                    (if you have cvs write access).  Please do not
+                    (if you have git write access).  Please do not
                     check in the generated files.
 clean               Remove all the built binary files.
-cvsclean            Remove all files that are generated automatically,
+gitclean            Remove all files that are generated automatically,
                     i.e. bring the tree back to the state as if it
-                    was checked out from the CVS.
+                    was checked out from the git.
 
 
 CONFIGURE OPTIONS AND BUILD VARIABLES
@@ -116,7 +109,7 @@ CONFIGUREARGS setting isn't affected.
 The build targets also creates a script 'pike' in the bin subdirectory
 which runs the built Pike directly without installing it first.  If
 you want to use Pike this way (which is mainly useful if you update
-from CVS often), you should consider doing 'make dump_modules' to make
+from git often), you should consider doing 'make dump_modules' to make
 it start faster.
 
 
@@ -195,7 +188,7 @@ Instructions if you want to do the build more manually:
    'make INSTALLARGS="--traditional" install' instead.
 
 After doing this, DO NOT commit the generated files.  They are placed
-in .cvsignore files so you shouldn't have to bother with them.
+in .gitignore files so you shouldn't have to bother with them.
 
 
 IF IT DOESN'T WORK