head	1.7;
access;
symbols
	TIGRIS_1_1_0RC2:1.4.6.1
	TIGRIS_1_1_0RC1:1.4.6.1
	TIGRIS_1_1:1.4.6.1.0.2
	TIGRIS_1_0_8:1.4.6.1
	TIGRIS_1_0_8RC3:1.4.6.1
	TIGRIS_1_0_8RC2:1.4.6.1
	TIGRIS_1_0_8RC1:1.4.6.1
	TIGRIS_1_0_7:1.4.6.1
	TIGRIS_1_0_7RC3:1.4.6.1
	TIGRIS_1_0_7RC2:1.4.6.1
	TIGRIS_1_0_7RC1:1.4.6.1
	TIGRIS_1_0_6:1.4.6.1
	TIGRIS_1_0_6RC5:1.4.6.1
	TIGRIS_1_0_6RC4:1.4.6.1
	TIGRIS_1_0_6RC3:1.4.6.1
	TIGRIS_1_0_6RC2:1.4.6.1
	TIGRIS_1_0_6RC1:1.4.6.1
	TIGRIS_1_0_5:1.4.6.1
	TIGRIS_1_0_5RC6:1.4.6.1
	TIGRIS_1_0_5RC5:1.4.6.1
	TIGRIS_1_0_5RC4:1.4.6.1
	TIGRIS_1_0_5RC3:1.4.6.1
	TIGRIS_1_0_5RC2:1.4
	TIGRIS_1_0_5RC1:1.4
	TIGRIS_1_0_4:1.4
	TIGRIS_1_0_3:1.4
	TIGRIS_1_0_2:1.4
	TIGRIS_1_0_1:1.4
	TIGRIS_1_0:1.4.0.6
	TIGRIS_1_0_0:1.4
	TIGRIS_1_0_0_RC1:1.4.0.2;
locks; strict;
comment	@# @;


1.7
date	2001.06.21.07.07.40;	author jefflove;	state Exp;
branches;
next	1.6;

1.6
date	2001.06.11.03.14.33;	author jefflove;	state Exp;
branches;
next	1.5;

1.5
date	2001.05.18.18.14.25;	author edk;	state Exp;
branches;
next	1.4;

1.4
date	2001.02.22.01.02.52;	author lori;	state Exp;
branches
	1.4.6.1;
next	1.3;

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

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

1.1
date	2001.01.29.19.42.33;	author lori;	state Exp;
branches;
next	;

1.4.6.1
date	2001.05.18.18.15.33;	author edk;	state Exp;
branches;
next	;


desc
@@


1.7
log
@html usage revision
@
text
@  <div class="docs" id="ddusingcvscommandline">
   <h2>Using command-line CVS to access project source files</h2>

   <div class="toc">
    <h4>CVS tool documents: Index</h4>

    <ul>
     <li>
      <a href="ddCVS.html">About source code version control with CVS</a> 

      <ul>
       <li><a href="ddCVS_cvsglossary.html">A version control glossary</a></li>

       <li>
        <strong>You are here:</strong> Using command-line CVS to access project source files 

        <ul>
         <li><a href="#cvsintro">Getting started with CVS</a></li>

         <li><a href="#accesscvs">Accessing a project's CVS repository</a></li>

         <li><a href="#gettingsource">Getting the source</a></li>

         <li><a href="#cvslog">Viewing file revision history</a></li>
        </ul>
       </li>

       <li><a href="ddCVS_cvscontributing.html">Contributing source code changes with CVS</a></li>

       <li><a href="ddCVS_cvsmanaging.html">Managing project files and directories with CVS</a></li>
      </ul>
     </li>
    </ul>
   </div>

   <div class="courtesylinks">
    <p><a href="/servlets/HelpTOC">Back to main Help index</a></p>
   </div>

   <h3><a id="cvsintro" name="cvsintro">Getting started with CVS</a></h3>

   <p>If you are participating in a development project on this site, you must use CVS as the versioning control tool for project source files. This the first in a series of three tool documents covering information and commands pertinent to using CVS.</p>

   <h3><a id="accesscvs" name="accesscvs">Accessing a project's CVS repository</a></h3>

   <p>If you do have cvs login access for a project hosted on this site, first you must set the cvsroot to access the project's source code repository. In your shell or terminal client, type:</p>

   <p><code>:pserver:yourlogin@@cvs.projectname.domain.com:/home/main_cvs_dir</code></p>

   <p>substituting your login and project information.</p>

   <p>If you are only working on one project at a time, you only have to set cvsroot the first time you log in to CVS.</p>

   <p>If you are participating in more than one project and need to access CVS repositories located on different servers, you need to set the cvsroot for each login session access the correct project's source repository.</p>

   <p>If you do not have a specific cvs login but wish to look at an open source project's source repository, you may still be able to log in to cvs as "anonymous" by typing:</p>

   <p><code>:pserver:anoncvs@@cvs.projectname.domain.com:/home/main_cvs_dir</code></p>

   <div class="courtesylinks">
    <p><a href="http://cvsbook.red-bean.com/cvsbook.html#Accessing_A_Repository">More about accessing a CVS repository</a></p>
   </div>

   <p>To log in to CVS, use the following command:</p>

   <p><code>cvs login</code></p>

   <p>Enter your user password when prompted. This should be the same password associated with your user account on this site.</p>

   <h3><a id="gettingsource" name="gettingsource">Getting source files</a></h3>

   <p>To get a "working copy" of the latest source files, you must check out the source files, a process which copies the files onto your system. First create a directory on your local machine by typing:</p>
<pre>
   <code>mkdir my_working_dir (the directory name of your choosing)
   cd my_working_dir</code>
 
</pre>

   <p>Then, to check out or copy source file from the repository into your newly created local directory, type:</p>

   <p><code>cvs checkout project_name</code></p>

   <p>This top-level module would contain the entire source code tree (that is, the top level directory and any subdirectories) for that part of the project. There is a fairly common module structure for project CVS repositories initially. As the project grows, the project's source "tree" also grows as subdirectories are added to various modules.</p>

   <p>To obtain the source code for a particular module called "module-name" within the project named "project_name", specify:</p>

   <p><code>cvs checkout module_name/project_name</code></p>

   <p><a href="http://cvsbook.red-bean.com/cvsbook.html#Checking_Out_A_Working_Copy">More about checking out a working copy of project files</a></p>

   <h3><a id="cvslog" name="cvslog">Viewing file revision history</a></h3>

   <p>Anyone with cvs read permission can view individual file histories to track revision information by typing:</p>

   <p><code>cvs log filename</code></p>

   <p>The result is a display of the file's revision information, starting with the most current revision, and includes such information as the log message, status, working revision number, and repository revision number.</p>

   <div class="courtesylinks">
    <p><a href="http://cvsbook.red-bean.com/cvsbook.html#Revision_Numbers">More about file revision numbers</a></p>

    <p><a id="cvsdiff" name="cvsdiff"><span class="HelpTextHeader">Comparing file revisions</span></a></p>
   </div>

   <p>To see the particulars of a file's modifications between two revisions, after obtaining file revision numbering information from the "<b>cvs log</b>" command's output, type:</p>

   <p><code>cvs diff -r revision_# -r revision_#</code></p>

   <p>The entire file contents display with lines from both versions where differences occur marked by revision number.</p>

   <div class="courtesylinks">
    <p><a href="http://cvsbook.red-bean.com/cvsbook.html#Finding_Out_What_You__And_Others__Did_--_update_And_diff">Finding out what you and others did</a><br />
     <a href="http://cvsbook.red-bean.com/cvsbook.html#diff">More about diffs and options</a></p>

    <p><a href="ddCVS_cvscontributing.html">More CVS help: Contributing your changes</a><br />
    <a href="/servlets/HelpTOC">Back to main Help index</a></p>
   </div>
  </div>
 


@


1.6
log
@extensive markup rework - first pass toward house xhtmlification
@
text
@d1 2
a2 10
<!DOCTYPE html PUBLIC "-//CollabNet//DTD XHTML 1.0 Transitional//EN"
"http://collabnet.com/dtds/collabnet_transitional_10.dtd">
<html>
 <head>
  <title>Using command-line CVS</title>
<style type="text/css">
 blockquote.c2 {font-weight: bold}
 div.c1 {margin-left: 2em}
</style>
 </head>
d4 2
a5 3
 <body>
  <div class="docs" id="docid">
<h2>Using command-line CVS to access project source files</h2>
d7 3
a9 1
  <p><b>CVS tool documents: Index</b></p>
d11 2
a12 3
  <div>
   <dl>
    <dt><a href="ddCVS.html">About source code version control with CVS</a></dt>
d14 2
a15 1
    <dt><a href="ddCVS_cvsglossary.html">A version control glossary</a></dt>
d17 2
a18 2
    <dd>
     <b>You are here: Using CVS to access project source files</b>
d20 1
a20 2
     <ul>
      <li><b><a href="#cvsintro"><b>Getting started with CVS</b></a></b></li>
d22 1
a22 1
      <li><a href="#accesscvs"><b>Accessing a project's CVS repository</b></a></li>
d24 3
a26 1
      <li><a href="#gettingsource"><b>Getting the source</b></a></li>
d28 1
a28 3
      <li><a href="#cvslog"><b>Viewing file revision history</b></a></li>
     </ul>
    </dd>
d30 5
a34 1
    <dd><a href="ddCVS_cvscontributing.html">Contributing source code changes with CVS</a></dd>
d36 3
a38 1
    <dd><a href="ddCVS_cvsmanaging.html">Managing project files and directories with CVS</a></dd>
d40 1
a40 5
    <dt><a href="/servlets/HelpTOC">Back to main Help index</a></dt>
   </dl>
  </div>
  
  <h3><a id="cvsintro" name="cvsintro">Getting started with CVS</a></h3>
d42 1
a42 1
  <p>If you are participating in a development project on this site, you must use CVS as the versioning control tool for project source files. This the first in a series of three tool documents covering information and commands pertinent to using CVS.</p>
d44 1
a44 3
  
  
  <h3><a id="accesscvs" name="accesscvs">Accessing a project's CVS repository</a></h3>
d46 1
a46 1
  <p>If you do have cvs login access for a project hosted on this site, first you must set the cvsroot to access the project's source code repository. In your shell or terminal client, type:</p>
d48 1
a48 3
  <blockquote class="c2">
   :pserver:yourlogin@@cvs.projectname.domain.com:/home/main_cvs_dir
  </blockquote>
d50 1
a50 1
  <p>substituting your login and project information.</p>
d52 1
a52 1
  <p>If you are only working on one project at a time, you only have to set cvsroot the first time you log in to CVS.</p>
d54 1
a54 1
  <p>If you are participating in more than one project and need to access CVS repositories located on different servers, you need to set the cvsroot for each login session access the correct project's source repository.</p>
d56 1
a56 1
  <p>If you do not have a specific cvs login but wish to look at an open source project's source repository, you may still be able to log in to cvs as "anonymous" by typing:</p>
d58 1
a58 3
  <blockquote class="c2">
   :pserver:anoncvs@@cvs.projectname.domain.com:/home/main_cvs_dir
  </blockquote>
d60 3
a62 1
  <p><a href="http://cvsbook.red-bean.com/cvsbook.html#Accessing_A_Repository">More about accessing a CVS repository</a></p>
d64 1
a64 1
  <p>To log in to CVS, use the following command:</p>
d66 1
a66 6
  <pre>
   <code>cvs login</code>
  </pre>
  <p>
Enter your user password when prompted. This should be the same password associated with your user account on this site. 
</p>
d68 1
a68 3
  
  
  <h3><a id="gettingsource" name="gettingsource">Getting source files</a></h3>
d70 1
a70 1
  <p>To get a "working copy" of the latest source files, you must check out the source files, a process which copies the files onto your system. First create a directory on your local machine by typing:</p>
d72 2
a73 1
  <pre>
d76 2
a77 1
  </pre>
d79 1
a79 1
  <p>Then, to check out or copy source file from the repository into your newly created local directory, type:</p>
d81 1
a81 3
  <blockquote class="c2">
   cvs checkout project_name
  </blockquote>
d83 1
a83 1
  <p>This top-level module would contain the entire source code tree (that is, the top level directory and any subdirectories) for that part of the project. There is a fairly common module structure for project CVS repositories initially. As the project grows, the project's source "tree" also grows as subdirectories are added to various modules.</p>
d85 1
a85 1
  <p>To obtain the source code for a particular module called "module-name" within the project named "project_name", specify:</p>
d87 1
a87 3
  <blockquote class="c2">
   cvs checkout module_name/project_name
  </blockquote>
d89 1
a89 1
  <p><a href="http://cvsbook.red-bean.com/cvsbook.html#Checking_Out_A_Working_Copy">More about checking out a working copy of project files</a></p>
d91 1
a91 3
  
  
  <h3><a id="cvslog" name="cvslog">Viewing file revision history</a></h3>
d93 1
a93 1
  <p>Anyone with cvs read permission can view individual file histories to track revision information by typing:</p>
d95 1
a95 3
  <blockquote class="c2">
   cvs log filename
  </blockquote>
d97 1
a97 1
  <p>The result is a display of the file's revision information, starting with the most current revision, and includes such information as the log message, status, working revision number, and repository revision number.</p>
d99 2
a100 1
  <p><a href="http://cvsbook.red-bean.com/cvsbook.html#Revision_Numbers">More about file revision numbers</a></p>
d102 2
a103 1
  <p><a id="cvsdiff" name="cvsdiff"><span class="HelpTextHeader">Comparing file revisions</span></a></p>
d105 1
a105 1
  <p>To see the particulars of a file's modifications between two revisions, after obtaining file revision numbering information from the "<b>cvs log</b>" command's output, type:</p>
d107 1
a107 3
  <blockquote class="c2">
   cvs diff -r revision_# -r revision_#
  </blockquote>
d109 1
a109 1
  <p>The entire file contents display with lines from both versions where differences occur marked by revision number.</p>
d111 3
a113 5
  <p><a href="http://cvsbook.red-bean.com/cvsbook.html#Finding_Out_What_You__And_Others__Did_--_update_And_diff">Finding out what you and others did</a><br />
  <a href="http://cvsbook.red-bean.com/cvsbook.html#diff">More about diffs and options</a></p>
  
  <div class="courtesylinks"><a href="ddCVS_cvscontributing.html">More CVS help: Contributing your changes</a><br />
<a href="/servlets/HelpTOC">Back to main Help index</a></div>
d115 5
a119 3
 </div>
</body>
</html>
@


1.5
log
@fix broken link
@
text
@d1 143
a143 119
<HTML>
<HEAD>
<TITLE>Using command-line CVS</TITLE>
</HEAD>
<BODY>
<TABLE BORDER="0" CELLSPACING="1" CELLPADDING="3" BORDER="0" WIDTH="100%">
  <TR>
    <SPAN CLASS="Header">Using command-line CVS to access project source files</SPAN>
<P>
<SPAN CLASS="PlainText"><B>CVS tool documents: Index</B>
<P>
<UL>
<DL>
<DT><A HREF="ddCVS.html">About source code version control with CVS</A>
<DT><A HREF="ddCVS_cvsglossary.html">A version control glossary</A>
<DD><B>You are here: Using CVS to access project source files
<UL>
	<LI><A HREF="#cvsintro"><B>Getting started with CVS</B></A>
	<LI><A HREF="#accesscvs"><B>Accessing a project's CVS repository</B></A>
	<LI><A HREF="#gettingsource"><B>Getting the source</B></A>
	<LI><A HREF="#cvslog"><B>Viewing file revision history</B></A>
</UL></B>
<DD><A HREF="ddCVS_cvscontributing.html">Contributing source code changes with CVS</A>
<DD><A HREF="ddCVS_cvsmanaging.html">Managing project files and directories with CVS</A>
<DT><A HREF="/servlets/HelpTOC">Back to main Help index</A>
</DL>
</UL>
<P>
<HR NOSHADE SIZE=1>
<A NAME="cvsintro"></A><SPAN CLASS="InputHeader">Getting started with CVS</SPAN>
<P>
If you are participating in a development project on this site, you must use CVS as the versioning control tool for project source files. This the first in a series of three tool documents covering information and commands pertinent to using CVS.
<P>

<HR NOSHADE SIZE=1>
<A NAME="accesscvs"></A><SPAN CLASS="InputHeader">Accessing a project's CVS repository</SPAN>
<P>
If you do have cvs login access for a project hosted on this site, first you must set the cvsroot to access the project's source code repository. In your shell or terminal client, type:
<BLOCKQUOTE>
 <B>:pserver:yourlogin@@cvs.projectname.domain.com:/home/main_cvs_dir</B>
</BLOCKQUOTE>
<P>substituting your login and project information.
<P>If you are only working on one project at a time, you only have to set cvsroot the first time you log in to CVS.
<P>If you are participating in more than one project and need to access CVS repositories located on different servers, you need to set the cvsroot for each login session access the correct project's source repository.
<P>
If you do not have a specific cvs login but wish to look at an open source project's source repository, you may still be able to log in to cvs as "anonymous" by typing:
<BLOCKQUOTE>
 <B>:pserver:anoncvs@@cvs.projectname.domain.com:/home/main_cvs_dir</B>
</BLOCKQUOTE>

<P>
<A HREF="http://cvsbook.red-bean.com/cvsbook.html#Accessing_A_Repository" TARGET=_NEW>More about accessing a CVS repository</A>
<P>
To log in to CVS, use the following command:<BR>
<BLOCKQUOTE>
          <B>cvs login</B><BR>
</BLOCKQUOTE>
          Enter your user password when prompted. This should be the same password associated with your user account on this site.
<P>

<HR NOSHADE SIZE=1>

<SPAN CLASS="InputHeader"><A NAME="gettingsource"></A>Getting source files</SPAN>
<P>
        To get a "working copy" of the latest source files, you must check out the source files, a process which copies the files onto your system. First create a directory on your local machine by typing:<BR>
<BLOCKQUOTE>
          <B>mkdir my_working_dir</B> (the directory name of your choosing)<BR>
          <B>cd my_working_dir</B><BR>
</BLOCKQUOTE>
<P>
Then, to check out or copy source file from the repository into your newly created local directory, type:
<BLOCKQUOTE>
          <B>cvs checkout project_name</B>
</BLOCKQUOTE>
<P>
This top-level module would contain the entire source code tree (that is, the top level directory and any subdirectories) for that part of the project. There is a fairly common module structure for project CVS repositories initially. As the project grows, the project's source "tree" also grows as subdirectories are added to various modules.
<P>
To obtain the source code for a particular module called "module-name" within the project named "project_name", specify:
<BLOCKQUOTE>
     <B>cvs checkout module_name/project_name</B>
</BLOCKQUOTE>
<P>
<A HREF="http://cvsbook.red-bean.com/cvsbook.html#Checking_Out_A_Working_Copy" TARGET=_NEW>More about checking out a working copy of project files</A>
<P>

<HR NOSHADE SIZE=1>

<A NAME="cvslog"></A><SPAN CLASS="InputHeader">Viewing file revision history</SPAN>
<P>
Anyone with cvs read permission can view individual file histories to track revision information by typing:
<BLOCKQUOTE>
<B>cvs log filename</B>
</BLOCKQUOTE>
<P>
The result is a display of the file's revision information, starting with the most current revision, and includes such information as the log message, status, working revision number, and repository revision number.
<P>
<A HREF="http://cvsbook.red-bean.com/cvsbook.html#Revision_Numbers" TARGET="_new">More about file revision numbers</A> 
<P>

<A NAME="cvsdiff"><SPAN CLASS="HelpTextHeader">Comparing file revisions</SPAN></A>
<P>
To see the particulars of a file's modifications between two revisions, after obtaining file revision numbering information from the &quot<B>cvs log</B>&quot command's output, type:
<BLOCKQUOTE>
<B>cvs diff -r revision_# -r revision_#</B>
</BLOCKQUOTE>
<P>
The entire file contents display with lines from both versions where differences occur marked by revision number.  
<P>

<A HREF="http://cvsbook.red-bean.com/cvsbook.html#Finding_Out_What_You__And_Others__Did_--_update_And_diff" TARGET="_new">Finding out what you and others did</A><BR>
<A HREF="http://cvsbook.red-bean.com/cvsbook.html#diff" TARGET="_new">More about diffs and options</A>

<HR NOSHADE SIZE=1>
<A HREF="ddCVS_cvscontributing.html">More CVS help: Contributing your changes</A><BR>
<A HREF="/servlets/HelpTOC">Back to main Help index</A></P></SPAN>

</SPAN>    
</TR>
</TABLE>
a144 2
</BODY>
</HTML>
@


1.4
log
@index revisions and other general html edits
@
text
@d114 1
a114 1
<A HREF="ddCVS_contributing.html">More CVS help: Contributing your changes</A><BR>
@


1.4.6.1
log
@fix broken link
@
text
@d114 1
a114 1
<A HREF="ddCVS_cvscontributing.html">More CVS help: Contributing your changes</A><BR>
@


1.3
log
@added <title> tags to all files
@
text
@d3 1
a3 3

<TITLE>Using Command-Line CVS</TITLE>

d8 9
a16 7
    <TD class="Header" nowrap>Using command-line CVS to access project source files</TD>
  </TR>
</TABLE>

<TABLE BORDER="0" CELLSPACING="2" CELLPADDING="2" BORDER="0" width="100%">
  <TR>
<span class="PlainText">
d18 9
a26 8
<dl>
<dt><A HREF="#accesscvs">Accessing a project's CVS repository</A>
<dt><A HREF="#gettingsource">Getting the source</A>
<dt><A HREF="#cvslog">Viewing file revision history</A>
	<dd><A HREF="#cvsdiff">Comparing revisions</A>


</dl>
d29 5
d35 2
a36 3

<P>
<P><span class="InputHeader"><A NAME="accesscvs">Accessing a project's CVS repository</A></span>
d39 3
a41 3
<blockquote>
 <b>:pserver:yourlogin@@cvs.projectname.domain.com:/home/main_cvs_dir</b>
</blockquote>
d48 1
a48 1
 <b>:pserver:anoncvs@@cvs.projectname.domain.com:/home/main_cvs_dir</b>
d52 1
a52 1
<A HREF="http://cvsbook.red-bean.com/cvsbook.html#Accessing_A_Repository" target=_new>More about accessing a CVS repository</a>
d55 2
a56 2
<blockquote>
          <b>cvs login</b><BR>
d61 1
a61 1
<HR noShade SIZE=1>
d63 1
a63 1
<span class="InputHeader"><A NAME="gettingsource"></A>Getting source files</span>
d67 2
a68 2
          <b>mkdir my_working_dir</b> (the directory name of your choosing)<BR>
          <b>cd my_working_dir</b><BR>
d73 1
a73 1
          <b>cvs checkout project_name</b>
d77 1
a77 1
<p>
d79 2
a80 2
<blockquote>
     <b>cvs checkout module_name/project_name</b>
d82 2
a83 2
<p>
<A HREF="http://cvsbook.red-bean.com/cvsbook.html#Checking_Out_A_Working_Copy" target=_new>More about checking out a working copy of project files</a>
d86 1
a86 1
<HR noShade SIZE=1>
d88 1
a88 1
<A NAME="cvslog"></A><span class="InputHeader">Viewing file revision history</SPAN>
d92 1
a92 1
<b>cvs log filename</B>
d97 2
a108 1
<A HREF="http://cvsbook.red-bean.com/cvsbook.html#diff" target="_new">More about diffs and options</A>
d110 6
a115 2
<HR noShade SIZE=1>
<a href="Help.html">Back to main Help index</a></p></span>
d117 2
a118 2
</span>    
</tr>
@


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


1.1
log
@new and revised help documentation for v1.0
@
text
@d1 103
a103 103
<TABLE BORDER="0" CELLSPACING="1" CELLPADDING="3" BORDER="0" WIDTH="100%">
  <TR>
    <TD class="Header" nowrap>Using command-line CVS to access project source files</TD>
  </TR>
</TABLE>

<TABLE BORDER="0" CELLSPACING="2" CELLPADDING="2" BORDER="0" width="100%">
  <TR>
<span class="PlainText">
<UL>
<dl>
<dt><A HREF="#accesscvs">Accessing a project's CVS repository</A>
<dt><A HREF="#gettingsource">Getting the source</A>
<dt><A HREF="#cvslog">Viewing file revision history</A>
	<dd><A HREF="#cvsdiff">Comparing revisions</A>


</dl>
</UL>
<P>


<P>
<P><span class="InputHeader"><A NAME="accesscvs">Accessing a project's CVS repository</A></span>
<P>
If you do have cvs login access for a project hosted on this site, first you must set the cvsroot to access the project's source code repository. In your shell or terminal client, type:
<blockquote>
 <b>:pserver:yourlogin@@cvs.projectname.domain.com:/home/main_cvs_dir</b>
</blockquote>
<P>substituting your login and project information.
<P>If you are only working on one project at a time, you only have to set cvsroot the first time you log in to CVS.
<P>If you are participating in more than one project and need to access CVS repositories located on different servers, you need to set the cvsroot for each login session access the correct project's source repository.
<P>
If you do not have a specific cvs login but wish to look at an open source project's source repository, you may still be able to log in to cvs as "anonymous" by typing:
<BLOCKQUOTE>
 <b>:pserver:anoncvs@@cvs.projectname.domain.com:/home/main_cvs_dir</b>
</BLOCKQUOTE>

<P>
<A HREF="http://cvsbook.red-bean.com/cvsbook.html#Accessing_A_Repository" target=_new>More about accessing a CVS repository</a>
<P>
To log in to CVS, use the following command:<BR>
<blockquote>
          <b>cvs login</b><BR>
</BLOCKQUOTE>
          Enter your user password when prompted. This should be the same password associated with your user account on this site.
<P>

<HR noShade SIZE=1>

<span class="InputHeader"><A NAME="gettingsource"></A>Getting source files</span>
<P>
        To get a "working copy" of the latest source files, you must check out the source files, a process which copies the files onto your system. First create a directory on your local machine by typing:<BR>
<BLOCKQUOTE>
          <b>mkdir my_working_dir</b> (the directory name of your choosing)<BR>
          <b>cd my_working_dir</b><BR>
</BLOCKQUOTE>
<P>
Then, to check out or copy source file from the repository into your newly created local directory, type:
<BLOCKQUOTE>
          <b>cvs checkout project_name</b>
</BLOCKQUOTE>
<P>
This top-level module would contain the entire source code tree (that is, the top level directory and any subdirectories) for that part of the project. There is a fairly common module structure for project CVS repositories initially. As the project grows, the project's source "tree" also grows as subdirectories are added to various modules.
<p>
To obtain the source code for a particular module called "module-name" within the project named "project_name", specify:
<blockquote>
     <b>cvs checkout module_name/project_name</b>
</BLOCKQUOTE>
<p>
<A HREF="http://cvsbook.red-bean.com/cvsbook.html#Checking_Out_A_Working_Copy" target=_new>More about checking out a working copy of project files</a>
<P>

<HR noShade SIZE=1>

<A NAME="cvslog"></A><span class="InputHeader">Viewing file revision history</SPAN>
<P>
Anyone with cvs read permission can view individual file histories to track revision information by typing:
<BLOCKQUOTE>
<b>cvs log filename</B>
</BLOCKQUOTE>
<P>
The result is a display of the file's revision information, starting with the most current revision, and includes such information as the log message, status, working revision number, and repository revision number.
<P>

<A NAME="cvsdiff"><SPAN CLASS="HelpTextHeader">Comparing file revisions</SPAN></A>
<P>
To see the particulars of a file's modifications between two revisions, after obtaining file revision numbering information from the &quot<B>cvs log</B>&quot command's output, type:
<BLOCKQUOTE>
<B>cvs diff -r revision_# -r revision_#</B>
</BLOCKQUOTE>
<P>
The entire file contents display with lines from both versions where differences occur marked by revision number.  
<P>
<A HREF="http://cvsbook.red-bean.com/cvsbook.html#diff" target="_new">More about diffs and options</A>

<HR noShade SIZE=1>
<a href="Help.html">Back to main Help index</a></p></span>

</span>    
</tr>
</TABLE>

@

