head	1.3;
access;
symbols
	dlr:1.1.1
	TIGRIS_0_9_2_4:1.1
	TIGRIS_0_9_2_3:1.1
	HELM_PEER_PORT_BRANCH:1.1.1.1
	TURBINE_PEER:1.1
	TIGRIS_0_9_2_1:1.1
	TIGRIS_0_9_2:1.1.0.6
	TIGRIS_0_8_4:1.1.0.4
	TIGRIS_0_9_0:1.1.0.2;
locks; strict;
comment	@# @;


1.3
date	2001.02.26.23.37.23;	author lori;	state dead;
branches;
next	1.2;

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

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

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

1.1.4.1
date	2001.01.16.00.17.44;	author susank;	state Exp;
branches;
next	;

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


desc
@@


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

<TITLE>CVS How-To</TITLE>

</HEAD>
<BODY>
<TABLE BORDER="0" CELLSPACING="1" CELLPADDING="3" BORDER="0" WIDTH="100%">
  <TR>
    <TD class="Header" nowrap>CVS How-To</TD>  
  </TR>
</TABLE>

<TABLE BORDER="0" CELLSPACING="2" CELLPADDING="2" BORDER="0" width="100%">
  <TR>
    <TD class="PlainText">
     <P>
      <A HREF="#cvscommandline">CVS command line samples</A><BR>
      <A HREF="#checkinaccess">Getting CVS check-in access on open source projects</A>
    </TD>
  </TR>
    <TR>
    <TD class="InputHeader" VALIGN="top"><A NAME="cvscommandline">CVS Command Line Examples</A></TD>
  </TR>
  <TR>
    <TD class="PlainText">
      <P>
      <OL>
        <LI>Set your CVSROOT environment variable to the value shown above </LI>
        <P><LI>Log into CVS with the command:<BR>
          <span class="TypewriterBold">cvs login</span><BR>
          and enter your user password when prompted. </LI>
        <P><LI>To get a copy of the latest source files:<BR>
          <span class="TypewriterBold">mkdir my_working_dir</span><BR>
          <span class="TypewriterBold">cd my_working_dir</span><BR>
          <span class="TypewriterBold">cvs checkout PROJECT_NAME/MODULE_NAME</span> </LI>
         <P><LI>To see the differences between your copy of a file and the latest version:<BR>
          <span class="TypewriterBold">cvs diff FILENAME</span> </LI>
         <P><LI>To compare your local directory against shared repository:<BR>
          <span class="TypewriterBold">cvs -qn update</span> </LI>
         <P><LI>To commit your changes to a shared repository<BR>
          (Your user account must have write permission)<BR>
          <span class="TypewriterBold">cvs commit -m "Type your changes message here" FILENAME</span> </LI>
         <P><LI>To commit your changes to all files in a directory and subdirectories:<BR>
          (Your user account must have write permission)<BR>
          <span class="TypewriterBold">cd top_directory_to_commit</span><BR>
          <span class="TypewriterBold">cvs commit -m "Type your changes message here"</span> </LI>
         <P><LI>To add a file to the shared repository:<BR>
          First create the file in the working directory of what you have checked out. Then type:<BR>
          <span class="TypewriterBold">cvs add FILENAME</span><BR>
          After you have made all additions, you will need to commit your changes. </LI>
         <P><LI>To remove a file from the shared repository:<BR>
          First delete the file from what you have checked out. Then type: <BR>
          <span class="TypewriterBold">cvs remove FILENAME</span><BR>
          After you have made all removals, you will need to commit your changes. </LI>
         <P><LI>To update your working directory with the latest changes from the shared repository (including any new directories):<BR>
          <span class="TypewriterBold">cd my_working_dir</span><BR>
          <span class="TypewriterBold">cvs update -d</span> </LI>
      </OL>

     <P><A HREF="http://www.gnu.org/manual/cvs/html_mono/cvs.html#SEC87" target="new">More CVS commands</A>
    </TD>
  </TR>
  </TR>
<P>
    <TR>
    <TD class="InputHeader" VALIGN="top"><P><A NAME="checkinaccess">Getting CVS check-in access on open source projects</A></TD>
  </TR>
  <TR>
    <TD class="PlainText">
     <P>
      <OL>
       <LI>
       Subscribe to <B>and regularly read</B> the relevant mailing
       lists so that you know what is going on in the particular area
       of development you are interested in.
     <P>
       <LI>
       When you post your first message to a discussion mailing list,
       introduce yourself and include the following:
     <P>
      <UL>
       <LI>who you are,<BR> 
       <LI>a few words on your background,<BR> 
       <LI>your interest in the project, and<BR> 
       <LI>what you would like to see happen with the project.<BR>
      </UL>
     <P>
       <LI>
       Make sure you have looked through the existing source code and
       understand what it is doing and how. If something is poorly
       documented, confusing, or you just can't grasp what is going
       on, ask on the associated mailing list for a summary.
     <P>
       <LI>
       Mention in writing that you understand the licensing governing
       the code that you will be working on, and your agreement that
       any changes you contribute are your own and these can be
       incorporated under that license.
     <P>
       <LI>
       Request project membership to gain check-in permissions on an
       area of the code base, and explain what sorts of things you are
       interested in doing with it. You will need to communicate
       frequently with the people who already maintain that area of
       code, so make sure there is consensus about what you should be
       working on.
     <P>
       <LI>
       When the project owner approves your project membership, you
       will get a CVS check-in account, probably restricted to a
       certain area. Make sure you understand which CVS branch you are
       supposed to be working on!
     <P>
       <LI>
       Submit some patches to establish that you know what you are doing. 
     <P>
       <LI>
       When you make modifications and enhancements, seek feedback and
       discussion about these on the associated mailing lists.
     </OL>
    </TD>
  </TR>
</TABLE>
</BODY>
</HTML>
@


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


1.1
log
@moved core documentation into helm, fewer overrides need to be in instances now
@
text
@d1 7
d125 2
@


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

<TITLE>CVS How-To</TITLE>

</HEAD>
<BODY>
a117 2
</BODY>
</HTML>
@


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

<TITLE>CVS How-To</TITLE>

</HEAD>
<BODY>
a117 2
</BODY>
</HTML>
@


1.1.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
@@

