Changeset f5bbc042 in rtems


Ignore:
Timestamp:
Mar 20, 2014, 9:16:39 PM (7 years ago)
Author:
Joel Sherrill <joel.sherrill@…>
Branches:
4.11, 5, master
Children:
a86d13a
Parents:
df40cc9
Message:

started/buildc.t: Change CVS to Git

File:
1 edited

Legend:

Unmodified
Added
Removed
  • doc/started/buildc.t

    rdf40cc9 rf5bbc042  
    11@c
    2 @c  COPYRIGHT (c) 1988-2013.
     2@c  COPYRIGHT (c) 1988-2014.
    33@c  On-Line Applications Research Corporation (OAR).
    44@c  All rights reserved.
     
    4848patches for a particular target architecture.
    4949
    50 All patches and RPM specification files are kept in CVS.  They are
    51 not included in release tarballs.  You will have to access the
    52 CVS branch for RTEMS @value{RTEMSAPI}.  For details on this,
    53 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
    54 instructions on accessing the RTEMS Source Code Repository in read-only mode.
    55 You can either do a complete checkout of the source tree or use a web
    56 interface.  A typical checkout command would look like this:
    57 @c TODO: pointing the user to the wiki entry might be enough.
    58 @example
    59 cvs -d :pserver:anoncvs@@www.rtems.org:/usr1/CVS -z 9 co -P rtems
    60 @end example
     50All patches and RPM specification files are kept under source code
     51control.  They are not included in release tarballs.  You will have to
     52access the CVS branch for RTEMS @value{RTEMSAPI}.  For details on this,
     53visit @uref{http://wiki.rtems.org/wiki/index.php/RTEMS_GIT_Repository,
     54http://wiki.rtems.org/wiki/index.php/RTEMS_GIT_Repository} and look for
     55instructions on accessing the RTEMS Source Code Repository in read-only
     56mode.
    6157
    6258In the checked out source code, you will need to look in the subdirectory
Note: See TracChangeset for help on using the changeset viewer.