head	1.7;
access;
symbols
	TIGRIS_1_1_0RC2:1.3.6.1
	TIGRIS_1_1_0RC1:1.3.6.1
	TIGRIS_1_1:1.3.6.1.0.2
	TIGRIS_1_0_8:1.3
	TIGRIS_1_0_8RC3:1.3
	TIGRIS_1_0_8RC2:1.3
	TIGRIS_1_0_8RC1:1.3
	TIGRIS_1_0_7:1.3
	TIGRIS_1_0_7RC3:1.3
	TIGRIS_1_0_7RC2:1.3
	TIGRIS_1_0_7RC1:1.3
	TIGRIS_1_0_6:1.3
	TIGRIS_1_0_6RC5:1.3
	TIGRIS_1_0_6RC4:1.3
	TIGRIS_1_0_6RC3:1.3
	TIGRIS_1_0_6RC2:1.3
	TIGRIS_1_0_6RC1:1.3
	TIGRIS_1_0_5:1.3
	TIGRIS_1_0_5RC6:1.3
	TIGRIS_1_0_5RC5:1.3
	TIGRIS_1_0_5RC4:1.3
	TIGRIS_1_0_5RC3:1.3
	TIGRIS_1_0_5RC2:1.3
	TIGRIS_1_0_5RC1:1.3
	TIGRIS_1_0_4:1.3
	TIGRIS_1_0_3:1.3
	TIGRIS_1_0_2:1.3
	TIGRIS_1_0_1:1.3
	TIGRIS_1_0:1.3.0.6
	TIGRIS_1_0_0:1.3
	TIGRIS_1_0_0_RC1:1.3.0.2
	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.4
	TIGRIS_0_8_4:1.2.0.2
	TIGRIS_0_9_0:1.1.0.2;
locks; strict;
comment	@# @;


1.7
date	2001.07.31.18.47.20;	author csjank;	state Exp;
branches;
next	1.6;

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

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

1.4
date	2001.03.29.20.13.26;	author csjank;	state Exp;
branches;
next	1.3;

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

1.2
date	2000.12.30.23.22.00;	author jrobbins;	state Exp;
branches
	1.2.2.1
	1.2.6.1;
next	1.1;

1.1
date	2000.12.22.08.45.24;	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.2.1
date	2001.01.16.00.17.44;	author susank;	state Exp;
branches;
next	1.2.2.2;

1.2.2.2
date	2001.01.31.20.44.24;	author amaley;	state Exp;
branches;
next	;

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

1.3.6.1
date	2001.07.31.19.29.14;	author csjank;	state Exp;
branches;
next	;


desc
@@


1.7
log
@removed reference to Help.html (file no longer exists)
@
text
@  <div class="docs" id="cvscheckout">
   <h2>CVS Checkout</h2>

   
  <p>You can use CVS to check out your own copies of project source code files 
    if you are a member of this project with CVS login access. CVS is an open 
    source version control for keeping track of all modifications to project source 
    code files. You can choose either a <a href="http://www.cvshome.org/downloads.html">command-line 
    CVS client</a> or <a href="http://www.wincvs.org/download.html">WinCvs</a> 
    with a Windows interface. What you can do with source files depends upon your 
    role in this project. (<a href="/project/www/docs/ProjectRoles.html">Roles?</a>)</p>

   <h3><a id="commandlinecvs" name="commandlinecvs">Command-line CVS checkout instructions</a></h3>

   <p>(<a href="#wincvs">Skip to WinCvs checkout instructions</a>)</p>

   <p>Before you can do a cvs checkout, you must set the cvsroot to indicate where the CVS repository for this project is located.</p>

   <ol>
    <li>
     The command to set cvsroot and login is: 

     <p><code>cvs -d :pserver:username@@projectname.domain.net:/cvs login</code></p>

     <p>(Substitute in your login for username, and the project name and associated domain, of course.)</p>

     <p>If this is the only project you working on, you only need to set the cvsroot once. Thereafter when you log in to this domain, the cvs repository for this project is assumed. If you are working multiple projects, however, you must specify the cvsroot each time you log in to ensure that the cvs repository you are accessing is the right one.</p>
    </li>

    <li>
     To check out the project source repository an individual module (if you don't need the entire repository), type: 

     <p><code>cvs -d :pserver:username@@projectname.domain.net:/cvs checkout [projectname]</code></p>

     <p>This command should result in a scrolling list of files being added to the local directory you specified on your machine. Now you are ready to use your file editor to work with individual files and make changes.</p>
    </li>
   </ol>

   <p>When you are ready to contribute your work into the project's CVS repository, you must <i>commit</i> each file you have modified into the project repository. But before you do that, you should set up an SSH tunnel for security purposes.</p>

   <div class="courtesylinks">
    <p><a href="/project/www/docs/DomainDocsSSHGuide.html">More about SSH tunneling</a><br />
     <a href="/project/www/docs/DomainDocsCVS.html">More about basic CVS commands and principles</a></p>
   </div>

   <h3><a id="wincvs" name="wincvs">WinCvs checkout instructions</a></h3>

   <p>To use WinCvs to check out your own set of source code files, you must first set up the correct cvs root using the following steps.</p>

   <ol>
    <li>
     Launch WinCvs and select <b>Cvs Admin - Preferences</b>. Enter the CVSroot: 

     <p><code>:pserver:username@@[projectname].[domain].net:/cvs</code></p>

     <p>Click OK.</p>
    </li>

    <li>If this your first cvs checkout, create a folder in Windows Explorer to hold all of your cvs project folders. Then create a subfolder for this project. (You may even want to create separate subfolders for each module if you're working in more than one.)</li>

    <li>In WinCvs, select <b>Cvs Admin - Login</b> and enter your cvs password.</li>

    <li>Click on the left window in the program and select a folder. Then select <b>Cvs Admin - Checkout Module</b>. Select the project folder you created earlier.</li>

    <li>Enter project module name and click OK. You should see a scrolling list of filenames as these are created in your folder(s).</li>

    <li>Repeat the module creation process for each additional cvs module you wish to check out.</li>
   </ol>
   <!--
             ##  This link is not working yet

             ## For more information, see <A
             ## HREF="/project/www/docs/wincvs_instructions.html">step-by-step
             ## WinCvs graphic tutorial</A> with instructions included for
             ## committing files.

             ## TODO: need some way to replace lost cvs passwords          

             -->

   <div class="courtesylinks">
    <p><a href="/project/www/docs/DomainDocsCVS.html#morecvsdoc">More CVS documentation</a></p>
   </div>
  </div>
 


@


1.6
log
@html usage revision
@
text
@d4 8
a11 1
   <p>You can use CVS to check out your own copies of project source code files if you are a member of this project with CVS login access. CVS is an open source version control for keeping track of all modifications to project source code files. You can choose either a <a href="http://www.cvshome.org/downloads.html">command-line CVS client</a> or <a href="http://www.wincvs.org/download.html">WinCvs</a> with a Windows interface. What you can do with source files depends upon your role in this project. (<a href="/project/www/docs/Help.html#ProjectRoles">Roles?</a>)</p>
@


1.5
log
@extensive markup rework - first pass toward house xhtmlification
@
text
@d1 2
a2 9
<!DOCTYPE html PUBLIC "-//CollabNet//DTD XHTML 1.0 Transitional//EN"
"http://collabnet.com/dtds/collabnet_transitional_10.dtd">
<html>
 <head>
  <title>CVS Checkout</title>
<style type="text/css">
 p.c1 {font-weight: bold}
</style>
 </head>
d4 1
a4 5
 <body>
<div class="docs" id="docid">
<h2>CVS Checkout</h2>
     <p>You can use CVS to check out your own copies of project source code files if you are a member of this project with CVS login access. CVS is an open source version control for keeping track of all modifications to project source code files. You can choose either a <a href="http://www.cvshome.org/downloads.html">command-line CVS client</a> or <a href="http://www.wincvs.org/download.html">WinCvs</a> with a Windows interface. What you can do with source files depends upon your role in this project. (<a href="/project/www/docs/Help.html#ProjectRoles">Roles?</a>)</p>
     <a id="commandlinecvs" name="commandlinecvs"></a>
d6 1
a6 1
     <h3>Command-line CVS checkout instructions</h3>
d8 1
a8 1
     <p>(<a href="#wincvs">Skip to WinCvs checkout instructions</a>)</p>
d10 1
a10 1
     <p>Before you can do a cvs checkout, you must set the cvsroot to indicate where the CVS repository for this project is located.</p>
d12 3
a14 3
     <ol>
      <li>
       The command to set cvsroot and login is: 
d16 1
a16 1
       <p>cvs -d :pserver:username@@projectname.domain.net:/cvs login</p>
d18 1
a18 1
       <p>(Substitute in your login for username, and the project name and associated domain, of course.)</p>
d20 2
a21 2
       <p>If this is the only project you working on, you only need to set the cvsroot once. Thereafter when you log in to this domain, the cvs repository for this project is assumed. If you are working multiple projects, however, you must specify the cvsroot each time you log in to ensure that the cvs repository you are accessing is the right one.</p>
      </li>
d23 2
a24 2
      <li>
       To check out the project source repository an individual module (if you don't need the entire repository), type: 
d26 1
a26 1
       <p>cvs -d :pserver:username@@projectname.domain.net:/cvs checkout [projectname]</p>
d28 3
a30 3
       <p>This command should result in a scrolling list of files being added to the local directory you specified on your machine. Now you are ready to use your file editor to work with individual files and make changes.</p>
      </li>
     </ol>
d32 1
a32 1
     <p>When you are ready to contribute your work into the project's CVS repository, you must <i>commit</i> each file you have modified into the project repository. But before you do that, you should set up an SSH tunnel for security purposes.</p>
d34 4
a37 2
     <p><a href="/project/www/docs/DomainDocsSSHGuide.html">More about SSH tunneling</a><br />
      <a href="/project/www/docs/DomainDocsCVS.html">More about basic CVS commands and principles</a></p>
d39 1
a39 1
     <h3><a id="wincvs" name="wincvs">WinCvs checkout instructions</a></h3>
d41 1
a41 1
     <p>To use WinCvs to check out your own set of source code files, you must first set up the correct cvs root using the following steps.</p>
d43 3
a45 3
     <ol>
      <li>
       Launch WinCvs and select <b>Cvs Admin - Preferences</b>. Enter the CVSroot: 
d47 1
a47 1
       <p>:pserver:username@@[projectname].[domain].net:/cvs</p>
d49 2
a50 2
       <p>Click OK.</p>
      </li>
d52 1
a52 1
      <li>If this your first cvs checkout, create a folder in Windows Explorer to hold all of your cvs project folders. Then create a subfolder for this project. (You may even want to create separate subfolders for each module if you're working in more than one.)</li>
d54 1
a54 1
      <li>In WinCvs, select <b>Cvs Admin - Login</b> and enter your cvs password.</li>
d56 1
a56 1
      <li>Click on the left window in the program and select a folder. Then select <b>Cvs Admin - Checkout Module</b>. Select the project folder you created earlier.</li>
d58 1
a58 1
      <li>Enter project module name and click OK. You should see a scrolling list of filenames as these are created in your folder(s).</li>
d60 4
a63 4
      <li>Repeat the module creation process for each additional cvs module you wish to check out.</li>
     </ol>
     <!--
          ##  This link is not working yet
d65 4
a68 4
          ## For more information, see <A
          ## HREF="/project/www/docs/wincvs_instructions.html">step-by-step
          ## WinCvs graphic tutorial</A> with instructions included for
          ## committing files.
d70 1
a70 1
          ## TODO: need some way to replace lost cvs passwords          
d72 1
a72 1
          -->
d74 5
a78 6
     <div class="courtesylinks">
      <a href="/project/www/docs/DomainDocsCVS.html#morecvsdoc">More CVS documentation</a>
     </div>
 </div>
</body>
</html>
@


1.4
log
@Changed html tags to lower case
@
text
@d1 2
d4 6
a9 1
<head>
d11 5
a15 1
<title>CVS Checkout</title>
d17 71
a87 125
</head>
<body>
<table border="0" width="100%">
<tr>
<td class="PlainText">
<p>
  You can use CVS to check out your own copies of project source code files if
  you are a member of this project with CVS login access. CVS is an
  open source version control for keeping track of all modifications
  to project source code files. You can choose either a <a
  href="http://www.cvshome.org/downloads.html">command-line CVS
  client</a> or <a
  href="http://www.wincvs.org/download.html">WinCvs</a> with a Windows
  interface. What you can do with source files depends upon your role
  in this project. (<a
  href="/project/www/docs/Help.html#ProjectRoles">Roles?</a>)
<p>

<a name="commandlinecvs"></a><span class="InputHeader">Command-line
CVS checkout instructions</span>&nbsp;&nbsp;&nbsp;(<a
href="#wincvs">Skip to WinCvs checkout instructions</a>)

<p>
Before you can do a cvs checkout, you must set the cvsroot to indicate
where the CVS repository for this project is located.

<ol>
<li>The command to set cvsroot and login is:
<p>
          <b>cvs -d :pserver:username@@projectname.domain.net:/cvs login</b>
<p>
(Substitute in your login for username, and the project name and associated domain, of course.)

<p>
If this is the only project you working on, you only need to set the
cvsroot once. Thereafter when you log in to this domain, the cvs
repository for this project is assumed. If you are working multiple
projects, however, you must specify the cvsroot each time you log in
to ensure that the cvs repository you are accessing is the right one.

<p>
<li>To check out the project source repository an individual module
(if you don't need the entire repository), type:

<p>
          <b>cvs -d :pserver:username@@projectname.domain.net:/cvs checkout [projectname]</b>
<p>
This command should result in a scrolling list of files being added to
the local directory you specified on your machine. Now you are ready
to use your file editor to work with individual files and make
changes.

</ol>

<p>
When you are ready to contribute your work into the project's CVS
repository, you must <i>commit</i> each file you have modified into
the project repository. But before you do that, you should set up an
SSH tunnel for security purposes.

<p>
<a href="/project/www/docs/DomainDocsSSHGuide.html">More about SSH tunneling</a><br>
<a href="/project/www/docs/DomainDocsCVS.html">More about basic CVS commands and principles</a>
<p>
<a name="wincvs"></a><span class="InputHeader">WinCvs checkout instructions</span><br>

<p>
To use WinCvs to check out your own set of source code files, you must
first set up the correct cvs root using the following steps.

<p>
<ol>
<li>Launch WinCvs and select <b>Cvs Admin - Preferences</b>. Enter the CVSroot:
<p>
<b>:pserver:username@@[projectname].[domain].net:/cvs</b>
<p>
Click OK.
<p>

<li>If this your first cvs checkout, create a folder in Windows
Explorer to hold all of your cvs project folders. Then create a
subfolder for this project. (You may even want to create separate
subfolders for each module if you're working in more than one.)
<p>

<li>In WinCvs, select <b>Cvs Admin - Login</b> and enter your cvs
password.

<p>
<li>Click on the left window in the program and select a folder. Then
select <b>Cvs Admin - Checkout Module</b>. Select the project folder
you created earlier.

<p>
<li>Enter project module name and click OK. You should see a scrolling
list of filenames as these are created in your folder(s).

<p>
<li>Repeat the module creation process for each additional cvs module
you wish to check out.
</ol>
</ul>



<!--
##  This link is not working yet

## For more information, see <A
## HREF="/project/www/docs/wincvs_instructions.html">step-by-step
## WinCvs graphic tutorial</A> with instructions included for
## committing files.

## TODO: need some way to replace lost cvs passwords          

-->

<hr size="1" noshade>

<a href="/project/www/docs/DomainDocsCVS.html#morecvsdoc">More CVS documentation</a>


</td>
</tr>
</table></body>
d89 2
@


1.3
log
@added <title> tags to all files
@
text
@d1 2
a2 2
<HTML>
<HEAD>
d4 1
a4 1
<TITLE>CVS Checkout</TITLE>
d6 2
a7 2
</HEAD>
<BODY>
d15 4
a18 4
  to project source code files. You can choose either a <A
  HREF="http://www.cvshome.org/downloads.html">command-line CVS
  client</A> or <A
  HREF="http://www.wincvs.org/download.html">WinCvs</A> with a Windows
d20 7
a26 7
  in this project. (<A
  HREF="/project/www/docs/Help.html#ProjectRoles">Roles?</A>)
<P>

<A NAME="commandlinecvs"></A><SPAN CLASS="InputHeader">Command-line
CVS checkout instructions</SPAN>&nbsp;&nbsp;&nbsp;(<A
HREF="#wincvs">Skip to WinCvs checkout instructions</A>)
d28 1
a28 1
<P>
d32 5
a36 5
<OL>
<LI>The command to set cvsroot and login is:
<P>
          <B>cvs -d :pserver:username@@projectname.domain.net:/cvs login</B>
<P>
d39 1
a39 1
<P>
d46 2
a47 2
<P>
<LI>To check out the project source repository an individual module
d50 3
a52 3
<P>
          <B>cvs -d :pserver:username@@projectname.domain.net:/cvs checkout [projectname]</B>
<P>
d58 1
a58 1
</OL>
d60 1
a60 1
<P>
d62 1
a62 1
repository, you must <I>commit</I> each file you have modified into
d66 5
a70 5
<P>
<A HREF="/project/www/docs/DomainDocsSSHGuide.html">More about SSH tunneling</A><BR>
<A HREF="/project/www/docs/DomainDocsCVS.html">More about basic CVS commands and principles</A>
<P>
<A NAME="wincvs"></A><SPAN CLASS="InputHeader">WinCvs checkout instructions</SPAN><BR>
d72 1
a72 1
<P>
d76 6
a81 6
<P>
<OL>
<LI>Launch WinCvs and select <B>Cvs Admin - Preferences</B>. Enter the CVSroot:
<P>
<B>:pserver:username@@[projectname].[domain].net:/cvs</B>
<P>
d83 1
a83 1
<P>
d85 1
a85 1
<LI>If this your first cvs checkout, create a folder in Windows
d89 1
a89 1
<P>
d91 1
a91 1
<LI>In WinCvs, select <B>Cvs Admin - Login</B> and enter your cvs
d94 3
a96 3
<P>
<LI>Click on the left window in the program and select a folder. Then
select <B>Cvs Admin - Checkout Module</B>. Select the project folder
d99 2
a100 2
<P>
<LI>Enter project module name and click OK. You should see a scrolling
d103 2
a104 2
<P>
<LI>Repeat the module creation process for each additional cvs module
d106 2
a107 2
</OL>
</UL>
d125 1
a125 1
<A HREF="/project/www/docs/DomainDocsCVS.html#morecvsdoc">More CVS documentation</A>
d130 2
a131 2
</table></BODY>
</HTML>
@


1.3.6.1
log
@
Issue number:
Obtained from:
Submitted by:
Reviewed by:
@
text
@d11 12
a22 11
      <p> You can use CVS to check out your own copies of project source code files 
        if you are a member of this project with CVS login access. CVS is an open 
        source version control for keeping track of all modifications to project 
        source code files. You can choose either a <A
  HREF="http://www.cvshome.org/downloads.html">command-line CVS client</A> or 
        <A
  HREF="http://www.wincvs.org/download.html">WinCvs</A> with a Windows interface. 
        What you can do with source files depends upon your role in this project. 
        (<A
  HREF="/project/www/docs/ProjectRoles.html">Roles?</A>) 
      <P>
@


1.2
log
@moved core documentation into helm, fewer overrides need to be in instances now
@
text
@d1 7
d130 2
a131 1
</table>@


1.2.6.1
log
@porting changes from the head to the branch
@
text
@a0 7
<HTML>
<HEAD>

<TITLE>CVS Checkout</TITLE>

</HEAD>
<BODY>
d123 1
a123 2
</table></BODY>
</HTML>
@


1.2.2.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.2.2
log
@updated links to wincvs.org now cvsgui.org
PR:
Obtained from:
Submitted by:
Reviewed by:
@
text
@d1 122
a122 122
<table border="0" width="100%">
<tr>
<td class="PlainText">
<p>
  You can use CVS to check out your own copies of project source code files if
  you are a member of this project with CVS login access. CVS is an
  open source version control for keeping track of all modifications
  to project source code files. You can choose either a <A
  HREF="http://www.cvshome.org/downloads.html">command-line CVS
  client</A> or <A
  HREF="http://www.cvsgui.org/download.html">WinCvs</A> with a Windows
  interface. What you can do with source files depends upon your role
  in this project. (<A
  HREF="/project/www/docs/Help.html#ProjectRoles">Roles?</A>)
<P>

<A NAME="commandlinecvs"></A><SPAN CLASS="InputHeader">Command-line
CVS checkout instructions</SPAN>&nbsp;&nbsp;&nbsp;(<A
HREF="#wincvs">Skip to WinCvs checkout instructions</A>)

<P>
Before you can do a cvs checkout, you must set the cvsroot to indicate
where the CVS repository for this project is located.

<OL>
<LI>The command to set cvsroot and login is:
<P>
          <B>cvs -d :pserver:username@@projectname.domain.net:/cvs login</B>
<P>
(Substitute in your login for username, and the project name and associated domain, of course.)

<P>
If this is the only project you working on, you only need to set the
cvsroot once. Thereafter when you log in to this domain, the cvs
repository for this project is assumed. If you are working multiple
projects, however, you must specify the cvsroot each time you log in
to ensure that the cvs repository you are accessing is the right one.

<P>
<LI>To check out the project source repository an individual module
(if you don't need the entire repository), type:

<P>
          <B>cvs -d :pserver:username@@projectname.domain.net:/cvs checkout [projectname]</B>
<P>
This command should result in a scrolling list of files being added to
the local directory you specified on your machine. Now you are ready
to use your file editor to work with individual files and make
changes.

</OL>

<P>
When you are ready to contribute your work into the project's CVS
repository, you must <I>commit</I> each file you have modified into
the project repository. But before you do that, you should set up an
SSH tunnel for security purposes.

<P>
<A HREF="/project/www/docs/DomainDocsSSHGuide.html">More about SSH tunneling</A><BR>
<A HREF="/project/www/docs/DomainDocsCVS.html">More about basic CVS commands and principles</A>
<P>
<A NAME="wincvs"></A><SPAN CLASS="InputHeader">WinCvs checkout instructions</SPAN><BR>

<P>
To use WinCvs to check out your own set of source code files, you must
first set up the correct cvs root using the following steps.

<P>
<OL>
<LI>Launch WinCvs and select <B>Cvs Admin - Preferences</B>. Enter the CVSroot:
<P>
<B>:pserver:username@@[projectname].[domain].net:/cvs</B>
<P>
Click OK.
<P>

<LI>If this your first cvs checkout, create a folder in Windows
Explorer to hold all of your cvs project folders. Then create a
subfolder for this project. (You may even want to create separate
subfolders for each module if you're working in more than one.)
<P>

<LI>In WinCvs, select <B>Cvs Admin - Login</B> and enter your cvs
password.

<P>
<LI>Click on the left window in the program and select a folder. Then
select <B>Cvs Admin - Checkout Module</B>. Select the project folder
you created earlier.

<P>
<LI>Enter project module name and click OK. You should see a scrolling
list of filenames as these are created in your folder(s).

<P>
<LI>Repeat the module creation process for each additional cvs module
you wish to check out.
</OL>
</UL>



<!--
##  This link is not working yet

## For more information, see <A
## HREF="/project/www/docs/wincvs_instructions.html">step-by-step
## WinCvs graphic tutorial</A> with instructions included for
## committing files.

## TODO: need some way to replace lost cvs passwords          

-->

<hr size="1" noshade>

<A HREF="/project/www/docs/DomainDocsCVS.html#morecvsdoc">More CVS documentation</A>


</td>
</tr>
@


1.1
log
@greatly simplified ProjectSource, moved help to CVSCheckout.html
@
text
@d17 8
a24 3
<A NAME="commandlinecvs"></A><SPAN CLASS="InputHeader">Command-line CVS checkout instructions</SPAN>&nbsp;&nbsp;&nbsp;(<A HREF="#wincvs">Skip to WinCvs checkout instructions</A>)
<P>
Before you can do a cvs checkout, you must set the cvsroot to indicate where the CVS repository for this project is located.
d31 1
d33 10
a42 3
If this is the only project you working on, you only need to set the cvsroot once. Thereafter when you log in to this domain, the cvs repository for this project is assumed. If you are working multiple projects, however, you must specify the cvsroot each time you log in to ensure that the cvs repository you are accessing is the right one.
<P>
<LI>To check out the project source repository an individual module (if you don't need the entire repository), type:
d46 5
a50 1
This command should result in a scrolling list of files being added to the local directory you specified on your machine. Now you are ready to use your file editor to work with individual files and make changes.
d52 1
d54 5
a58 1
When you are ready to contribute your work into the project's CVS repository, you must <I>commit</I> each file you have modified into the project repository. But before you do that, you should set up an SSH tunnel for security purposes.
d64 1
d66 3
a68 1
To use WinCvs to check out your own set of source code files, you must first set up the correct cvs root using the following steps.
d77 19
a95 7
<LI>If this your first cvs checkout, create a folder in Windows Explorer to hold all of your cvs project folders. Then create a subfolder for this project. (You may even want to create separate subfolders for each module if you're working in more than one.)
<P>
<LI>In WinCvs, select <B>Cvs Admin - Login</B> and enter your cvs password.
<P>
<LI>Click on the left window in the program and select a folder. Then select <B>Cvs Admin - Checkout Module</B>. Select the project folder you created earlier.
<P>
<LI>Enter project module name and click OK. You should see a scrolling list of filenames as these are created in your folder(s).
d97 2
a98 1
<LI>Repeat the module creation process for each additional cvs module you wish to check out.
@


1.1.1.1
log
@Replacing the HEAD with the HELM_PEER_PORT_BRANCH.
@
text
@a0 7
<HTML>
<HEAD>

<TITLE>CVS Checkout</TITLE>

</HEAD>
<BODY>
d17 1
a17 4
<A NAME="commandlinecvs"></A><SPAN CLASS="InputHeader">Command-line
CVS checkout instructions</SPAN>&nbsp;&nbsp;&nbsp;(<A
HREF="#wincvs">Skip to WinCvs checkout instructions</A>)

d19 1
a19 3
Before you can do a cvs checkout, you must set the cvsroot to indicate
where the CVS repository for this project is located.

a25 1

d27 1
a27 6
If this is the only project you working on, you only need to set the
cvsroot once. Thereafter when you log in to this domain, the cvs
repository for this project is assumed. If you are working multiple
projects, however, you must specify the cvsroot each time you log in
to ensure that the cvs repository you are accessing is the right one.

d29 1
a29 3
<LI>To check out the project source repository an individual module
(if you don't need the entire repository), type:

d33 1
a33 5
This command should result in a scrolling list of files being added to
the local directory you specified on your machine. Now you are ready
to use your file editor to work with individual files and make
changes.

a34 1

d36 1
a36 5
When you are ready to contribute your work into the project's CVS
repository, you must <I>commit</I> each file you have modified into
the project repository. But before you do that, you should set up an
SSH tunnel for security purposes.

a41 1

d43 1
a43 3
To use WinCvs to check out your own set of source code files, you must
first set up the correct cvs root using the following steps.

d52 1
a52 5

<LI>If this your first cvs checkout, create a folder in Windows
Explorer to hold all of your cvs project folders. Then create a
subfolder for this project. (You may even want to create separate
subfolders for each module if you're working in more than one.)
d54 1
a54 4

<LI>In WinCvs, select <B>Cvs Admin - Login</B> and enter your cvs
password.

d56 1
a56 4
<LI>Click on the left window in the program and select a folder. Then
select <B>Cvs Admin - Checkout Module</B>. Select the project folder
you created earlier.

d58 1
a58 3
<LI>Enter project module name and click OK. You should see a scrolling
list of filenames as these are created in your folder(s).

d60 1
a60 2
<LI>Repeat the module creation process for each additional cvs module
you wish to check out.
d85 1
a85 2
</table></BODY>
</HTML>
@


