[rtems commit] started/buildrt.t: Change CVS to Git

[Joel Sherrill]

Module:    rtems
Branch:    master
Commit:    df40cc90168df3dbd91056a1886f6cca7cac70f0
Changeset: http://git.rtems.org/rtems/commit/?id=df40cc90168df3dbd91056a1886f6cca7cac70f0

Author:    Joel Sherrill <joel.sherrill at oarcorp.com>
Date:      Thu Mar 20 16:16:02 2014 -0500

started/buildrt.t: Change CVS to Git

---

 doc/started/buildrt.t |   18 ++++++------------
 1 files changed, 6 insertions(+), 12 deletions(-)

diff --git a/doc/started/buildrt.t b/doc/started/buildrt.t
index 51d2e4a..c242296 100644
--- a/doc/started/buildrt.t
+++ b/doc/started/buildrt.t
@@ -1,5 +1,5 @@
 @c
- at c  COPYRIGHT (c) 1988-2010.
+ at c  COPYRIGHT (c) 1988-2014.
 @c  On-Line Applications Research Corporation (OAR).
 @c  All rights reserved.
 
@@ -41,19 +41,13 @@ tar xjf ../archive/rtems- at value{RTEMSAPI}.<VERSION>.tar.bz2
 
 This creates the directory rtems- at value{RTEMSAPI}.<VERSION>
 
- at section Obtaining the RTEMS Source from CVS
+ at section Obtaining the RTEMS Source from Git
 
 Instead of downloading release tarballs you may choose to check out the current
-RTEMS source from CVS. For details on accessing RTEMS CVS repository consult
- at uref{http://www.rtems.org/wiki/index.php/RTEMS_CVS_Repository, http://www.rtems.org/wiki/index.php/RTEMS_CVS_Repository}.  The steps required
-to obtain the source code from CVS are usually like the following:
- at example
-$ cvs -d :pserver:anoncvs@@www.rtems.org:/usr1/CVS login
-Logging in to :pserver:anoncvs@@www.rtems.org:2401/usr1/CVS
-CVS password:
-$ cvs -d :pserver:anoncvs@@www.rtems.org:/usr1/CVS -z 9 co -P rtems  # for the main RTEMS source
-$ cvs -d :pserver:anoncvs@@www.rtems.org:/usr1/CVS -z 9 co -P examples-v2  # for examples
- at end example
+RTEMS source from the project's source code repository. For details on
+accessing the RTEMS source repository consult:
+
+ at uref{http://wiki.rtems.org/wiki/index.php/RTEMS_GIT_Repository, http://wiki.rtems.org/wiki/index.php/RTEMS_GIT_Repository}.
 
 @section Add <INSTALL_POINT>/bin to Executable PATH