Remove anonymous cvs instructions, and replace them with instructions

for git. Change other references from cvs to git as well.

Author: mhagander

doc/src/sgml/Makefile

@@ -8,7 +8,7 @@
 
 # This makefile is for building and installing the documentation.
 # When a release tarball is created, the documentation files are
-# prepared using the distprep target.  In CVS-based trees these files
+# prepared using the distprep target.  In Git-based trees these files
 # don't exist, unless explicitly built, so we skip the installation in
 # that case.
 

doc/src/sgml/acronyms.sgml

@@ -292,7 +292,7 @@
     <listitem>
      <para>
       <ulink
-      url="http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/backend/access/heap/README.HOT">Heap-Only
+      url="http://git.postgresql.org/gitweb?p=postgresql.git;a=blob;f=src/backend/access/heap/README.HOT;hb=HEAD">Heap-Only
       Tuples</ulink>
      </para>
     </listitem>

doc/src/sgml/cvs.sgml

@@ -137,12 +137,12 @@
 
 <!-- appendixes -->
 <!entity contacts   SYSTEM "contacts.sgml">
-<!entity cvs        SYSTEM "cvs.sgml">
 <!entity datetime   SYSTEM "datetime.sgml">
 <!entity docguide   SYSTEM "docguide.sgml">
 <!entity errcodes   SYSTEM "errcodes.sgml">
 <!entity features   SYSTEM "features.sgml">
 <!entity keywords   SYSTEM "keywords.sgml">
+<!entity sourcerepo SYSTEM "sourcerepo.sgml">
 
 <!entity release    SYSTEM "release.sgml">
 <!entity release-9.1    SYSTEM "release-9.1.sgml">

doc/src/sgml/filelist.sgml

@@ -176,7 +176,7 @@ $ENV{PATH}=$ENV{PATH} . ';c:\some\where\bison\bin';
      <term><productname>Bison</productname> and
       <productname>Flex</productname></term>
      <listitem><para>
-      Bison and Flex are required to build from CVS, but not required when
+      Bison and Flex are required to build from Git, but not required when
       building from a release file. Note that only Bison 1.875 or versions
       2.2 and later will work. Also, Flex version 2.5.31 or later is required.
       Bison can be downloaded from <ulink url="http://gnuwin32.sourceforge.net"></>.

doc/src/sgml/install-win32.sgml

@@ -274,7 +274,7 @@ su - postgres
   </para>
 
   <para>
-   If you are building from a <acronym>CVS</acronym> tree instead of
+   If you are building from a <productname>Git</productname> tree instead of
    using a released source package, or if you want to do server development,
    you also need the following packages:
 
@@ -295,7 +295,7 @@ su - postgres
       </indexterm>
 
       GNU <application>Flex</> and <application>Bison</>
-      are needed to build from a CVS checkout, or if you changed the actual
+      are needed to build from a Git checkout, or if you changed the actual
       scanner and parser definition files. If you need them, be sure
       to get <application>Flex</> 2.5.31 or later and
       <application>Bison</> 1.875 or later. Other <application>lex</>
@@ -308,7 +308,7 @@ su - postgres
        <primary>perl</primary>
       </indexterm>
 
-      <application>Perl</> 5.8 or later is needed to build from a CVS checkout,
+      <application>Perl</> 5.8 or later is needed to build from a Git checkout,
       or if you changed the input files for any of the build steps that
       use Perl scripts.  If building on Windows you will need
       <application>Perl</> in any case.
@@ -361,7 +361,7 @@ su - postgres
 
   <para>
    You can also get the source directly from the version control repository, see
-   <xref linkend="cvs">.
+   <xref linkend="sourcerepo">.
   </para>
  </sect1>
 ]]>
@@ -2562,7 +2562,7 @@ make MAX_CONNECTIONS=5 check
    <para>
     Aside from the PostgreSQL source distribution, you will need GNU
     make (HP's make will not do), and either GCC or HP's full ANSI C
-    compiler.  If you intend to build from CVS sources rather than a
+    compiler.  If you intend to build from Git sources rather than a
     distribution tarball, you will also need Flex (GNU lex) and Bison
     (GNU yacc).  We also recommend making sure you are fairly
     up-to-date on HP patches.  At a minimum, if you are building 64

doc/src/sgml/installation.sgml

@@ -258,7 +258,7 @@
   &release;
   &contrib;
   &external-projects;
-  &cvs;
+  &sourcerepo;
   &docguide;
   &acronyms;
 

doc/src/sgml/postgres.sgml

@@ -228,8 +228,8 @@
       If the function or the options do not exist then your version is
       more than old enough to warrant an upgrade.
       If you run a prepackaged version, such as RPMs, say so, including any
-      subversion the package might have. If you are talking about a CVS
-      snapshot, mention that, including its date and time.
+      subversion the package might have. If you are talking about a Git
+      snapshot, mention that, including the commit hash.
      </para>
 
      <para>

doc/src/sgml/problems.sgml

@@ -49,14 +49,12 @@ can be created without links to the main documentation.  Don't use <xref>.
 
   <para>
    A complete list of changes for each release can be obtained by
-   viewing the <link linkend="cvs">CVS</link> logs for each release.
+   viewing the <link linkend="git">Git</link> logs for each release.
    The <ulink
    url="http://archives.postgresql.org/pgsql-committers/"><literal>pgsql-committers</literal>
    email list</ulink> records all source code changes as well.  There is also
-   a <ulink url="http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/">web
+   a <ulink url="http://git.postgresql.org/gitweb?p=postgresql.git;a=summary">web
    interface</ulink> that shows changes to specific files.
-   <!-- we need a file containing the CVS logs for each release, and something
-   like the SVN web interface that groups commits but has branches -->
   </para>
 
   <para>