replace mentions of CVS with GIT in docuemntation files

5 files changed, 11 insertions, 15 deletions

diff --git a/HACKING b/HACKING
index 47297c02..267f008a 100644
--- a/HACKING
+++ b/HACKING
@@ -11,7 +11,7 @@ the <systemtap@sources.redhat.com> mailing list.
   and after your changes, and regressions avoided, explained, or
   corrected.
 
-  Established contributors may be considered for direct CVS write
+  Established contributors may be considered for direct GIT write
   access.  Other contributors should simply pack up the goods into a
   plain text email message to the mailing list.
 
diff --git a/README b/README
index 0ea30508..addb7187 100644
--- a/README
+++ b/README
@@ -31,13 +31,9 @@ Build steps:
   ftp://sources.redhat.com/pub/systemtap/elfutils/elfutils-NNNN.tar.gz
   ftp://sources.redhat.com/pub/systemtap/elfutils/elfutils-portability.patch
 - Untar the snapshot in some new directory; apply patch (don't ask, long story)
-- Download systemtap sources snapshot or from CVS or GIT:
+- Download systemtap sources snapshot or from GIT:
   ftp://sources.redhat.com/pub/systemtap/snapshots/ 
   (or)
-  cvs -d :pserver:anoncvs@sources.redhat.com:/cvs/systemtap login
-  # enter "anoncvs" as the password
-  cvs -d :pserver:anoncvs@sources.redhat.com:/cvs/systemtap co src
-  (or)
   git clone git://sources.redhat.com/git/systemtap.git
       (or) http://sources.redhat.com/git/systemtap.git
 - Build it:
diff --git a/doc/langref.tex b/doc/langref.tex
index 973769d4..46d350f6 100644
--- a/doc/langref.tex
+++ b/doc/langref.tex
@@ -3267,7 +3267,7 @@ For more information, see:
 \item The SystemTap tutorial at \url{http://sourceware.org/systemtap/tutorial/}
 \item The SystemTap wiki at \url{http://sourceware.org/systemtap/wiki}
 \item The SystemTap documentation page at \url{http://sourceware.org/systemtap/documentation.html}
-\item From an unpacked source tarball or CVS directory, the examples in in the
+\item From an unpacked source tarball or GIT directory, the examples in in the
 src/examples directory, the tapsets in the src/tapset directory, and the
 test scripts in the src/testsuite directory.
 \item The man pages for tapsets. For a list, run the command \texttt{{}``man -k
diff --git a/doc/tutorial.tex b/doc/tutorial.tex
index ee7d37da..58673467 100644
--- a/doc/tutorial.tex
+++ b/doc/tutorial.tex
@@ -1053,7 +1053,7 @@ as study, modification, and sharing.}
 Finally, there is the project web site
 (\verb+http://sources.redhat.com/systemtap/+) with several articles,
 an archived public mailing list for users and developers
-(\verb+systemtap@sources.redhat.com+), and a live CVS source
+(\verb+systemtap@sources.redhat.com+), and a live GIT source
 repository.  Come join us!
 
 
diff --git a/tapset/DEVGUIDE b/tapset/DEVGUIDE
index 44c4890c..3d550319 100644
--- a/tapset/DEVGUIDE
+++ b/tapset/DEVGUIDE
@@ -106,7 +106,7 @@ of "Tapset files", "Namespace" and "Embedded C & Safety."
 
 Tapset files
 ------------
-Tapset files are stored in src/tapset in the SystemTap CVS directory.  
+Tapset files are stored in src/tapset in the SystemTap GIT directory.  
 Most are kept at that level. If you have code that only works on a specific
 architecture or kernel-version, you may choose to put that in the
 corresponding subdirectories.
@@ -161,7 +161,7 @@ Update other Makefiles as necessary.
 Test cases
 ----------
 All tapsets should be accompanied by test scripts.  The tests are kept
-in src/testsuite in CVS and based on dejagnu.  You must have dejagnu and
+in src/testsuite in GIT and based on dejagnu.  You must have dejagnu and
 expect installed on your system to run the tests.
 
 Your tests should validate that:
@@ -182,7 +182,7 @@ most important, it validates that the tapset can actually be used for
 something useful.  If you can't write a script that uses the tapset in a
 meaningful way, perhaps you should rethink what the tapset provides.
 
-Example scripts are stored in src/examples in CVS.
+Example scripts are stored in src/examples in GIT.
 
 Change Logs
 -----------
@@ -211,7 +211,7 @@ mailing list archive is found at http://sources.redhat.com/ml/systemtap/.
 The systemtap-cvs mailing list archive is at
 http://sources.redhat.com/ml/systemtap-cvs/.
 
-You can request CVS write access at
+You can request GIT write access at
 http://sources.redhat.com/cgi-bin/pdw/ps_form.cgi.
 
 
@@ -227,11 +227,11 @@ you with SystemTap:
 - SystemTap project home page
   (http://sourceware.org/systemtap/index.html)
 
-- SystemTap mailing lists, IRC channels and CVS instructions
+- SystemTap mailing lists, IRC channels and GIT instructions
   (http://sourceware.org/systemtap/getinvolved.html)
 
-- CVS repository
-  (http://sources.redhat.com/cgi-bin/cvsweb.cgi/src/?cvsroot=systemtap)
+- GIT repository
+  (http://sources.redhat.com/git/?p=systemtap.git;a=summary
 
 - HACKING file in the source directory.  This file outlines what's 
   expected of project contributors.