head	1.5;
access;
symbols
	dlr:1.1.1
	TIGRIS_0_9_2_4:1.2
	TIGRIS_0_9_2_3:1.2
	HELM_PEER_PORT_BRANCH:1.1.1.1
	TURBINE_PEER:1.2
	TIGRIS_0_9_2_1:1.2
	TIGRIS_0_9_2:1.2.0.6
	TIGRIS_0_8_4:1.2.0.4
	TIGRIS_0_9_0:1.2.0.2;
locks; strict;
comment	@# @;


1.5
date	2001.02.26.23.36.56;	author lori;	state dead;
branches;
next	1.4;

1.4
date	2001.02.11.18.29.47;	author jrobbins;	state Exp;
branches;
next	1.3;

1.3
date	2001.02.09.00.59.20;	author susank;	state Exp;
branches;
next	1.2;

1.2
date	2001.01.09.18.22.52;	author dlr;	state Exp;
branches
	1.2.4.1
	1.2.8.1;
next	1.1;

1.1
date	2000.12.30.23.22.00;	author jrobbins;	state Exp;
branches
	1.1.1.1;
next	;

1.1.1.1
date	2001.02.21.00.31.51;	author dlr;	state Exp;
branches;
next	;

1.2.4.1
date	2001.01.16.00.17.44;	author susank;	state Exp;
branches;
next	1.2.4.2;

1.2.4.2
date	2001.01.31.20.44.24;	author amaley;	state Exp;
branches;
next	1.2.4.3;

1.2.4.3
date	2001.02.02.20.11.42;	author amaley;	state Exp;
branches;
next	;

1.2.8.1
date	2001.02.17.18.39.15;	author edk;	state Exp;
branches;
next	;


desc
@@


1.5
log
@removed file; obsoleted by 1.0 help
@
text
@<HTML>
<HEAD>

<TITLE>Source Code Version Control: CVS</TITLE>

</HEAD>
<BODY>
<TABLE BORDER="0" CELLSPACING="1" CELLPADDING="3" BORDER="0" WIDTH="100%">
  <TR>
    <TD class="Header" nowrap>Source code version control: CVS</TD>  
  </TR>
</TABLE>
<TABLE BORDER="0" CELLSPACING="2" CELLPADDING="2" BORDER="0" width="100%">
  <TR>
    <TD class="PlainText">
      <P>

  <dl>
        <dt><A HREF="#aboutcvs">About CVS</A></dt>
        <dd><A HREF="DomainDocsCVS_cvsprimer.html">A version control primer (basic concepts)</A>
        <dt><A HREF="#accesscvs">Accessing a project's CVS repository</A></dt>
        <dd><A HREF="DomainDocsCVS_cvs_how-to.html">CVS How-Two command-line example</a><br> 
        <dd><A HREF="DomainDocsSourceBrowse.html">Source code browsing</A></dd>
        <dt><A HREF="#morecvsdoc">Further CVS documentation</A></dt>
  </dl>


      <P><span class="InputHeader"><A NAME="aboutcvs">About CVS</A></span>

      <P>The Concurrent Versions System (CVS) is a version control system for keeping track of all modifications to project source code files. CVS is widely used in both open source and proprietary software development projects, and is generally considered to be the best freely available, full-featured version control tool. Two special features make CVS particularly suited to collaborative development across the Internet: 

<OL>
<LI>The use of file merging rather than locking. File locking prohibits other developers from accessing a file when someone else has checked it out. CVS allows a multiple check-outs of a single file, and then combines all the changes.
<P>
<LI>Remote access to source code file repositories. Developers can obtain and modify project files from virtually anywhere.
</OL>

     <P>CVS is a client-server system. The CVS repository is maintained on a web server; clients run on users' machines and connect to the server via the Internet. Clients are available for nearly all platforms including: UNIX, Windows, Macintosh, and any Java-based platform.
     <P>

      <span class="InputHeader">CVS allows you to:</span>
      <UL>
        <LI>Check out source files and directories</LI>
        <LI>View differences between versions</LI>
        <LI>View change log comments</LI>
        <LI>Commit changes made in your local copy of the source files to the main source code repository</LI>
        <LI>Do many other tasks; see links below</LI>
      </UL>

      <P><span class="InputHeader"><A NAME="accesscvs">Accessing your project's CVS repository</A></span>
      <P>For instructions on using CVS for a specific project: 
     <OL>
       <LI>From your Project Home page, click on Source Code in the project menu
       <LI>Choose whether to download source code archives, browse the CVS repository, or to  of how to checkout CVS project/module files, which includes the location of your project's repository (CVSROOT).
       </OL>  
     <BLOCKQUOTE>
      <P>For command-line access to the CVS source code repository, use the following CVSROOT: <P>
      <b>:pserver:anoncvs@@cvs.PROJECT_NAME.DOMAIN.com:/home/MAIN_CVS_DIR</b></P>

       <P>You may use the login "anoncvs" with password "anoncvs" to gain read-only CVS access. If you have been given "write" access to the CVS repository, then replace "anoncvs" with your own login (e.g., "mylogin@@cvs.PROJECT_NAME.DOMAIN.com") and use your own user password.</P>

       <P>Read the "source/CVS" page for each project and/or component to learn how the source code is organized into CVS modules. For example, to get the source code for a module ("MODULE_NAME") in your project ("PROJECT_NAME"), you should checkout "MODULE_NAME/PROJECT_NAME". This is the top-level module containing the entire source code tree for that particular module. Other modules may contain the documentation and web site files associated with this module.
	 </BLOCKQUOTE>

    <span class="InputHeader"><A NAME="morecvsdoc">Further CVS Documentation</A> </span>    
     <UL>
      <LI><A href="http://www.gnu.org/manual/cvs/index.html" target=_new>CVS Manual</A></LI>

      <LI><A href="http://www.cyclic.com/" target=_new>CVS Home Page at Cyclic</A></LI>

      <LI><A href="http://www.loria.fr/~molli/cvs-index.html" target=_new>Pascal Molli's CVS page</A></LI>

      <LI><A href="http://dmoz.org/Computers/Software/Configuration_Management/Tools/CVS/" target=_new>CVS Page on Dmoz</A></LI>
     </UL>

     <span class="InputHeader">CVS Clients</span>
     <UL>
     <LI><A
      HREF="http://www.cvshome.org/downloads.html" target="_new">Command line clients for many systems</A></LI>

      <LI><A HREF="http://www.wincvs.org/" target="_new">WinCVS: a Windows CVS client</A></LI>

      <LI><A HREF="http://www.jcvs.org/" target="_new">jCVS: a Java CVS client</A></LI>

      <LI><A HREF="http://cervisia.sourceforge.net" target="_new">Cervisia: a KDE CVS Client</A></LI>
     </UL>

     <span class="InputHeader">CVS Books</span>
     <UL>
      <LI><A HREF="http://www.amazon.com/exec/obidos/ISBN=0132408546/cyclicsoftwareA/"  target="_new">Practical Software Configuration Management</A> </LI>
      <LI><A HREF="http://cvsbook.red-bean.com/" target="_new">Open Source Development with CVS (many chapters free online)</A></LI>
     </UL>
    </TD>
  </TR>
</TABLE>
</BODY>
</HTML>
@


1.4
log
@added <title> tags to all files
@
text
@@


1.3
log
@removed window's nasty line breaks, and corrected more links in HelpBox files
PR:
Obtained from:
Submitted by:
Reviewed by:
@
text
@d1 7
d96 2
@


1.2
log
@Link directly to the live list of CVS command line clients, rather
than to a redirect to it.
@
text
@d1 88
a88 88
<TABLE BORDER="0" CELLSPACING="1" CELLPADDING="3" BORDER="0" WIDTH="100%">
  <TR>
    <TD class="Header" nowrap>Source code version control: CVS</TD>  
  </TR>
</TABLE>
<TABLE BORDER="0" CELLSPACING="2" CELLPADDING="2" BORDER="0" width="100%">
  <TR>
    <TD class="PlainText">
      <P>

  <dl>
        <dt><A HREF="#aboutcvs">About CVS</A></dt>
        <dd><A HREF="DomainDocsCVS_cvsprimer.html">A version control primer (basic concepts)</A>
        <dt><A HREF="#accesscvs">Accessing a project's CVS repository</A></dt>
        <dd><A HREF="DomainDocsCVS_cvs_how-to.html">CVS How-Two command-line example</a><br> 
        <dd><A HREF="DomainDocsSourceBrowse.html">Source code browsing</A></dd>
        <dt><A HREF="#morecvsdoc">Further CVS documentation</A></dt>
  </dl>


      <P><span class="InputHeader"><A NAME="aboutcvs">About CVS</A></span>

      <P>The Concurrent Versions System (CVS) is a version control system for keeping track of all modifications to project source code files. CVS is widely used in both open source and proprietary software development projects, and is generally considered to be the best freely available, full-featured version control tool. Two special features make CVS particularly suited to collaborative development across the Internet: 

<OL>
<LI>The use of file merging rather than locking. File locking prohibits other developers from accessing a file when someone else has checked it out. CVS allows a multiple check-outs of a single file, and then combines all the changes.
<P>
<LI>Remote access to source code file repositories. Developers can obtain and modify project files from virtually anywhere.
</OL>

     <P>CVS is a client-server system. The CVS repository is maintained on a web server; clients run on users' machines and connect to the server via the Internet. Clients are available for nearly all platforms including: UNIX, Windows, Macintosh, and any Java-based platform.
     <P>

      <span class="InputHeader">CVS allows you to:</span>
      <UL>
        <LI>Check out source files and directories</LI>
        <LI>View differences between versions</LI>
        <LI>View change log comments</LI>
        <LI>Commit changes made in your local copy of the source files to the main source code repository</LI>
        <LI>Do many other tasks; see links below</LI>
      </UL>

      <P><span class="InputHeader"><A NAME="accesscvs">Accessing your project's CVS repository</A></span>
      <P>For instructions on using CVS for a specific project: 
     <OL>
       <LI>From your Project Home page, click on Source Code in the project menu
       <LI>Choose whether to download source code archives, browse the CVS repository, or to  of how to checkout CVS project/module files, which includes the location of your project's repository (CVSROOT).
       </OL>  
     <BLOCKQUOTE>
      <P>For command-line access to the CVS source code repository, use the following CVSROOT: <P>
      <b>:pserver:anoncvs@@cvs.PROJECT_NAME.DOMAIN.com:/home/MAIN_CVS_DIR</b></P>

       <P>You may use the login "anoncvs" with password "anoncvs" to gain read-only CVS access. If you have been given "write" access to the CVS repository, then replace "anoncvs" with your own login (e.g., "mylogin@@cvs.PROJECT_NAME.DOMAIN.com") and use your own user password.</P>

       <P>Read the "source/CVS" page for each project and/or component to learn how the source code is organized into CVS modules. For example, to get the source code for a module ("MODULE_NAME") in your project ("PROJECT_NAME"), you should checkout "MODULE_NAME/PROJECT_NAME". This is the top-level module containing the entire source code tree for that particular module. Other modules may contain the documentation and web site files associated with this module.
	 </BLOCKQUOTE>

    <span class="InputHeader"><A NAME="morecvsdoc">Further CVS Documentation</A> </span>    
     <UL>
      <LI><A href="http://www.gnu.org/manual/cvs/index.html" target=_new>CVS Manual</A></LI>

      <LI><A href="http://www.cyclic.com/" target=_new>CVS Home Page at Cyclic</A></LI>

      <LI><A href="http://www.loria.fr/~molli/cvs-index.html" target=_new>Pascal Molli's CVS page</A></LI>

      <LI><A href="http://dmoz.org/Computers/Software/Configuration_Management/Tools/CVS/" target=_new>CVS Page on Dmoz</A></LI>
     </UL>

     <span class="InputHeader">CVS Clients</span>
     <UL>
     <LI><A
      HREF="http://www.cvshome.org/downloads.html" target="_new">Command line clients for many systems</A></LI>

      <LI><A HREF="http://www.wincvs.org/" target="_new">WinCVS: a Windows CVS client</A></LI>

      <LI><A HREF="http://www.jcvs.org/" target="_new">jCVS: a Java CVS client</A></LI>

      <LI><A HREF="http://cervisia.sourceforge.net" target="_new">Cervisia: a KDE CVS Client</A></LI>
     </UL>

     <span class="InputHeader">CVS Books</span>
     <UL>
      <LI><A HREF="http://www.amazon.com/exec/obidos/ISBN=0132408546/cyclicsoftwareA/"  target="_new">Practical Software Configuration Management</A> </LI>
      <LI><A HREF="http://cvsbook.red-bean.com/" target="_new">Open Source Development with CVS (many chapters free online)</A></LI>
     </UL>
    </TD>
  </TR>
</TABLE>
@


1.2.8.1
log
@porting changes from the head to the branch
@
text
@d1 88
a88 97
<HTML>
<HEAD>

<TITLE>Source Code Version Control: CVS</TITLE>

</HEAD>
<BODY>
<TABLE BORDER="0" CELLSPACING="1" CELLPADDING="3" BORDER="0" WIDTH="100%">
  <TR>
    <TD class="Header" nowrap>Source code version control: CVS</TD>  
  </TR>
</TABLE>
<TABLE BORDER="0" CELLSPACING="2" CELLPADDING="2" BORDER="0" width="100%">
  <TR>
    <TD class="PlainText">
      <P>

  <dl>
        <dt><A HREF="#aboutcvs">About CVS</A></dt>
        <dd><A HREF="DomainDocsCVS_cvsprimer.html">A version control primer (basic concepts)</A>
        <dt><A HREF="#accesscvs">Accessing a project's CVS repository</A></dt>
        <dd><A HREF="DomainDocsCVS_cvs_how-to.html">CVS How-Two command-line example</a><br> 
        <dd><A HREF="DomainDocsSourceBrowse.html">Source code browsing</A></dd>
        <dt><A HREF="#morecvsdoc">Further CVS documentation</A></dt>
  </dl>


      <P><span class="InputHeader"><A NAME="aboutcvs">About CVS</A></span>

      <P>The Concurrent Versions System (CVS) is a version control system for keeping track of all modifications to project source code files. CVS is widely used in both open source and proprietary software development projects, and is generally considered to be the best freely available, full-featured version control tool. Two special features make CVS particularly suited to collaborative development across the Internet: 

<OL>
<LI>The use of file merging rather than locking. File locking prohibits other developers from accessing a file when someone else has checked it out. CVS allows a multiple check-outs of a single file, and then combines all the changes.
<P>
<LI>Remote access to source code file repositories. Developers can obtain and modify project files from virtually anywhere.
</OL>

     <P>CVS is a client-server system. The CVS repository is maintained on a web server; clients run on users' machines and connect to the server via the Internet. Clients are available for nearly all platforms including: UNIX, Windows, Macintosh, and any Java-based platform.
     <P>

      <span class="InputHeader">CVS allows you to:</span>
      <UL>
        <LI>Check out source files and directories</LI>
        <LI>View differences between versions</LI>
        <LI>View change log comments</LI>
        <LI>Commit changes made in your local copy of the source files to the main source code repository</LI>
        <LI>Do many other tasks; see links below</LI>
      </UL>

      <P><span class="InputHeader"><A NAME="accesscvs">Accessing your project's CVS repository</A></span>
      <P>For instructions on using CVS for a specific project: 
     <OL>
       <LI>From your Project Home page, click on Source Code in the project menu
       <LI>Choose whether to download source code archives, browse the CVS repository, or to  of how to checkout CVS project/module files, which includes the location of your project's repository (CVSROOT).
       </OL>  
     <BLOCKQUOTE>
      <P>For command-line access to the CVS source code repository, use the following CVSROOT: <P>
      <b>:pserver:anoncvs@@cvs.PROJECT_NAME.DOMAIN.com:/home/MAIN_CVS_DIR</b></P>

       <P>You may use the login "anoncvs" with password "anoncvs" to gain read-only CVS access. If you have been given "write" access to the CVS repository, then replace "anoncvs" with your own login (e.g., "mylogin@@cvs.PROJECT_NAME.DOMAIN.com") and use your own user password.</P>

       <P>Read the "source/CVS" page for each project and/or component to learn how the source code is organized into CVS modules. For example, to get the source code for a module ("MODULE_NAME") in your project ("PROJECT_NAME"), you should checkout "MODULE_NAME/PROJECT_NAME". This is the top-level module containing the entire source code tree for that particular module. Other modules may contain the documentation and web site files associated with this module.
	 </BLOCKQUOTE>

    <span class="InputHeader"><A NAME="morecvsdoc">Further CVS Documentation</A> </span>    
     <UL>
      <LI><A href="http://www.gnu.org/manual/cvs/index.html" target=_new>CVS Manual</A></LI>

      <LI><A href="http://www.cyclic.com/" target=_new>CVS Home Page at Cyclic</A></LI>

      <LI><A href="http://www.loria.fr/~molli/cvs-index.html" target=_new>Pascal Molli's CVS page</A></LI>

      <LI><A href="http://dmoz.org/Computers/Software/Configuration_Management/Tools/CVS/" target=_new>CVS Page on Dmoz</A></LI>
     </UL>

     <span class="InputHeader">CVS Clients</span>
     <UL>
     <LI><A
      HREF="http://www.cvshome.org/downloads.html" target="_new">Command line clients for many systems</A></LI>

      <LI><A HREF="http://www.wincvs.org/" target="_new">WinCVS: a Windows CVS client</A></LI>

      <LI><A HREF="http://www.jcvs.org/" target="_new">jCVS: a Java CVS client</A></LI>

      <LI><A HREF="http://cervisia.sourceforge.net" target="_new">Cervisia: a KDE CVS Client</A></LI>
     </UL>

     <span class="InputHeader">CVS Books</span>
     <UL>
      <LI><A HREF="http://www.amazon.com/exec/obidos/ISBN=0132408546/cyclicsoftwareA/"  target="_new">Practical Software Configuration Management</A> </LI>
      <LI><A HREF="http://cvsbook.red-bean.com/" target="_new">Open Source Development with CVS (many chapters free online)</A></LI>
     </UL>
    </TD>
  </TR>
</TABLE>
</BODY>
</HTML>
@


1.2.4.1
log
@adding the generic, default docs into this branch, bc they are in the head and nec for instantiations using stable branches
@
text
@@


1.2.4.2
log
@updated links to wincvs.org now cvsgui.org
PR:
Obtained from:
Submitted by:
Reviewed by:
@
text
@d74 1
a74 1
      <LI><A HREF="http://www.cvsgui.org/" target="_new">WinCVS: a Windows CVS client</A></LI>
@


1.2.4.3
log
@fixed typo in Fourth link at top of page "CVS How TO command-line ex"
R:
Obtained from:
Submitted by:
Reviewed by:
@
text
@d15 1
a15 1
        <dd><A HREF="DomainDocsCVS_cvs_how-to.html">CVS How-To command-line example</a><br> 
@


1.1
log
@moved core documentation into helm, fewer overrides need to be in instances now
@
text
@d72 1
a72 1
      HREF="http://www.cyclic.com/downloads.html" target="_new">Command line clients for many systems</A></LI>
@


1.1.1.1
log
@Replacing the HEAD with the HELM_PEER_PORT_BRANCH.
@
text
@d1 88
a88 97
<HTML>
<HEAD>

<TITLE>Source Code Version Control: CVS</TITLE>

</HEAD>
<BODY>
<TABLE BORDER="0" CELLSPACING="1" CELLPADDING="3" BORDER="0" WIDTH="100%">
  <TR>
    <TD class="Header" nowrap>Source code version control: CVS</TD>  
  </TR>
</TABLE>
<TABLE BORDER="0" CELLSPACING="2" CELLPADDING="2" BORDER="0" width="100%">
  <TR>
    <TD class="PlainText">
      <P>

  <dl>
        <dt><A HREF="#aboutcvs">About CVS</A></dt>
        <dd><A HREF="DomainDocsCVS_cvsprimer.html">A version control primer (basic concepts)</A>
        <dt><A HREF="#accesscvs">Accessing a project's CVS repository</A></dt>
        <dd><A HREF="DomainDocsCVS_cvs_how-to.html">CVS How-Two command-line example</a><br> 
        <dd><A HREF="DomainDocsSourceBrowse.html">Source code browsing</A></dd>
        <dt><A HREF="#morecvsdoc">Further CVS documentation</A></dt>
  </dl>


      <P><span class="InputHeader"><A NAME="aboutcvs">About CVS</A></span>

      <P>The Concurrent Versions System (CVS) is a version control system for keeping track of all modifications to project source code files. CVS is widely used in both open source and proprietary software development projects, and is generally considered to be the best freely available, full-featured version control tool. Two special features make CVS particularly suited to collaborative development across the Internet: 

<OL>
<LI>The use of file merging rather than locking. File locking prohibits other developers from accessing a file when someone else has checked it out. CVS allows a multiple check-outs of a single file, and then combines all the changes.
<P>
<LI>Remote access to source code file repositories. Developers can obtain and modify project files from virtually anywhere.
</OL>

     <P>CVS is a client-server system. The CVS repository is maintained on a web server; clients run on users' machines and connect to the server via the Internet. Clients are available for nearly all platforms including: UNIX, Windows, Macintosh, and any Java-based platform.
     <P>

      <span class="InputHeader">CVS allows you to:</span>
      <UL>
        <LI>Check out source files and directories</LI>
        <LI>View differences between versions</LI>
        <LI>View change log comments</LI>
        <LI>Commit changes made in your local copy of the source files to the main source code repository</LI>
        <LI>Do many other tasks; see links below</LI>
      </UL>

      <P><span class="InputHeader"><A NAME="accesscvs">Accessing your project's CVS repository</A></span>
      <P>For instructions on using CVS for a specific project: 
     <OL>
       <LI>From your Project Home page, click on Source Code in the project menu
       <LI>Choose whether to download source code archives, browse the CVS repository, or to  of how to checkout CVS project/module files, which includes the location of your project's repository (CVSROOT).
       </OL>  
     <BLOCKQUOTE>
      <P>For command-line access to the CVS source code repository, use the following CVSROOT: <P>
      <b>:pserver:anoncvs@@cvs.PROJECT_NAME.DOMAIN.com:/home/MAIN_CVS_DIR</b></P>

       <P>You may use the login "anoncvs" with password "anoncvs" to gain read-only CVS access. If you have been given "write" access to the CVS repository, then replace "anoncvs" with your own login (e.g., "mylogin@@cvs.PROJECT_NAME.DOMAIN.com") and use your own user password.</P>

       <P>Read the "source/CVS" page for each project and/or component to learn how the source code is organized into CVS modules. For example, to get the source code for a module ("MODULE_NAME") in your project ("PROJECT_NAME"), you should checkout "MODULE_NAME/PROJECT_NAME". This is the top-level module containing the entire source code tree for that particular module. Other modules may contain the documentation and web site files associated with this module.
	 </BLOCKQUOTE>

    <span class="InputHeader"><A NAME="morecvsdoc">Further CVS Documentation</A> </span>    
     <UL>
      <LI><A href="http://www.gnu.org/manual/cvs/index.html" target=_new>CVS Manual</A></LI>

      <LI><A href="http://www.cyclic.com/" target=_new>CVS Home Page at Cyclic</A></LI>

      <LI><A href="http://www.loria.fr/~molli/cvs-index.html" target=_new>Pascal Molli's CVS page</A></LI>

      <LI><A href="http://dmoz.org/Computers/Software/Configuration_Management/Tools/CVS/" target=_new>CVS Page on Dmoz</A></LI>
     </UL>

     <span class="InputHeader">CVS Clients</span>
     <UL>
     <LI><A
      HREF="http://www.cvshome.org/downloads.html" target="_new">Command line clients for many systems</A></LI>

      <LI><A HREF="http://www.wincvs.org/" target="_new">WinCVS: a Windows CVS client</A></LI>

      <LI><A HREF="http://www.jcvs.org/" target="_new">jCVS: a Java CVS client</A></LI>

      <LI><A HREF="http://cervisia.sourceforge.net" target="_new">Cervisia: a KDE CVS Client</A></LI>
     </UL>

     <span class="InputHeader">CVS Books</span>
     <UL>
      <LI><A HREF="http://www.amazon.com/exec/obidos/ISBN=0132408546/cyclicsoftwareA/"  target="_new">Practical Software Configuration Management</A> </LI>
      <LI><A HREF="http://cvsbook.red-bean.com/" target="_new">Open Source Development with CVS (many chapters free online)</A></LI>
     </UL>
    </TD>
  </TR>
</TABLE>
</BODY>
</HTML>
@


