[PATCH 02/10] started/buildc.t: Change CVS to Git

[Joel Sherrill]

---
 doc/started/buildc.t |   20 ++++++++------------
 1 files changed, 8 insertions(+), 12 deletions(-)

diff --git a/doc/started/buildc.t b/doc/started/buildc.t
index baf53a9..a16c9f2 100644
--- a/doc/started/buildc.t
+++ b/doc/started/buildc.t
@@ -1,5 +1,5 @@
 @c
- at c  COPYRIGHT (c) 1988-2013.
+ at c  COPYRIGHT (c) 1988-2014.
 @c  On-Line Applications Research Corporation (OAR).
 @c  All rights reserved.
 
@@ -47,17 +47,13 @@ determine the current versions and, if a patch is required, what version.
 This section describes how to locate the appropriate tool versions and
 patches for a particular target architecture.
 
-All patches and RPM specification files are kept in CVS.  They are
-not included in release tarballs.  You will have to access the
-CVS branch for RTEMS @value{RTEMSAPI}.  For details on this,
-visit @uref{http://www.rtems.org/wiki/index.php/RTEMS_CVS_Repository, http://www.rtems.org/wiki/index.php/RTEMS_CVS_Repository} and look for
-instructions on accessing the RTEMS Source Code Repository in read-only mode.
-You can either do a complete checkout of the source tree or use a web
-interface.  A typical checkout command would look like this:
- at c TODO: pointing the user to the wiki entry might be enough.
- at example
-cvs -d :pserver:anoncvs@@www.rtems.com:/usr1/CVS -z 9 co -P rtems
- at end example
+All patches and RPM specification files are kept under source code
+control.  They are not included in release tarballs.  You will have to
+access the CVS branch for RTEMS @value{RTEMSAPI}.  For details on this,
+visit @uref{http://wiki.rtems.org/wiki/index.php/RTEMS_GIT_Repository,
+http://wiki.rtems.org/wiki/index.php/RTEMS_GIT_Repository} and look for
+instructions on accessing the RTEMS Source Code Repository in read-only
+mode.
 
 In the checked out source code, you will need to look in the subdirectory
 @code{contrib/crossrpms/autotools} to determine the versions of AUTOCONF
-- 
1.7.1