Change Subversion to GIT in various places

diff --git a/docs/README b/docs/README
index 676d660ae29a40638c4ac14661e6e80a6bb2584f..afb048d4d4a4d89ac575c64e022960250189d5ed 100644 (file)
--- a/docs/README
+++ b/docs/README
@@ -67,9 +67,9 @@ overview:
 - 'make install' installs the HTML docs in
   $(install)/share/doc/valgrind/html/, if they are present.  (They will
   be present if you are installing from the result of a 'make dist'.
-  They might not be present if you are developing in a Subversion
-  workspace and have not built them.)  It doesn't install the XML docs,
-  as they're not useful installed.
+  They might not be present if you are developing in a git workspace and
+  have not built them.)  It doesn't install the XML docs, as they're not
+  useful installed.
 
 If the XML processing tools ever mature enough to become standard, we
 could just build the docs from XML when doing 'make install', which

diff --git a/docs/internals/directory-structure.txt b/docs/internals/directory-structure.txt
index a03e3fd141c2bdae807a0043ad46abba38277302..559a2fcb0decd95b2b11768d0f2fbcf01f44e6cc 100644 (file)
--- a/docs/internals/directory-structure.txt
+++ b/docs/internals/directory-structure.txt
@@ -64,9 +64,8 @@ version of rgrep, use a command something like this:
 
    find . -name '*.h' \
           -type f \
-          -not -path '*.svn\/*' | xargs grep "$1"
+          -not -path '*.git\/*' | xargs grep "$1"
 
 The -name option gives the file wildcard, the -type says "look in normal
-files only" and the -not -path tells it to not look in Subversions hidden
-directories.
+files only" and the -not -path tells it to not look in git hidden directories.
 

diff --git a/docs/internals/qemu-aarch64-linux-HOWTO.txt b/docs/internals/qemu-aarch64-linux-HOWTO.txt
index 56c855d37347e78c983577443a44bbe6c4325da0..61ae53189ff00e495d94796eaaa35ded0dce7ba6 100644 (file)
--- a/docs/internals/qemu-aarch64-linux-HOWTO.txt
+++ b/docs/internals/qemu-aarch64-linux-HOWTO.txt
@@ -97,6 +97,6 @@ ssh -XC -p 5555 username@localhost
 
   (on the guest)
   become root
-  apt-get install make gcc g++ automake autoconf emacs subversion gdb
+  apt-get install make gcc g++ automake autoconf emacs git gdb
 
 Hack on, etc.

diff --git a/docs/internals/qemu-mips64-linux-HOWTO.txt b/docs/internals/qemu-mips64-linux-HOWTO.txt
index 9ba94234b346d33c70ebd0c3818f91525f09be7d..d94e022c32b586b1ba01e7daf30713341e5aa499 100644 (file)
--- a/docs/internals/qemu-mips64-linux-HOWTO.txt
+++ b/docs/internals/qemu-mips64-linux-HOWTO.txt
@@ -101,7 +101,7 @@ ssh -XC -p 5555 username@localhost
   (on the guest)
   become root
 
-  apt-get install make g++ gcc subversion emacs gdb automake autoconf
+  apt-get install make g++ gcc git emacs gdb automake autoconf
   apt-get gcc-multilib g++-multilib
 
 Configuring V on the guest:

diff --git a/docs/xml/manual-writing-tools.xml b/docs/xml/manual-writing-tools.xml
index bbba74769321193a767bbd1e800d66b1d0c9b140..7a2fc0dfdd99a75d6bee47cabd729f9122dbeaee 100644 (file)
--- a/docs/xml/manual-writing-tools.xml
+++ b/docs/xml/manual-writing-tools.xml
@@ -53,8 +53,8 @@ when the <option>--tool</option> option is used to select it.</para>
 <title>Getting the code</title>
 
 <para>To write your own tool, you'll need the Valgrind source code.  You'll
-need a check-out of the Subversion repository for the automake/autoconf
-build instructions to work.  See the information about how to do check-out
+need a clone from the git repository for the automake/autoconf
+build instructions to work.  See the information about how to do clone
 from the repository at <ulink url="&vg-repo-url;">the Valgrind
 website</ulink>.</para>
 

diff --git a/nightly/README.txt b/nightly/README.txt
index 85ad0636af6c521a27dd922d206e331da2b6b809..0592dc43aa0f237c316d077fe01f35c693675c84 100644 (file)
--- a/nightly/README.txt
+++ b/nightly/README.txt
@@ -186,7 +186,7 @@ If something goes wrong, looking at the output files can be useful.  For
 example, if no email was sent but you expected one, check sendmail.log to
 see if the mailer script had a problem.  Or check if unchanged.log exists.
 
-Occasionally the SVN server isn't available when the tests runs, for either
+Occasionally the git server isn't available when the tests runs, for either
 or both trees.  When this happens the email will be sent but it won't be
 very informative.  Usually it's just a temporary server problem and it'll
 run fine the next time without you having to do anything.
@@ -195,7 +195,7 @@ Note that the test suite is imperfect:
 - There are very few machines where all tests pass;  that's why the old/new
   diff is produced.  Some of the tests may not be as portable as intended.
 - Some tests are non-deterministic, and so may pass one day and fail the
-  next.  
+  next.
 
 Improving the test suite to avoid these problems is a long-term goal but it
 isn't easy.