[wwwdocs] Further shorten cvs.html

Message ID alpine.LFD.2.02.1101081749020.4533@ybpnyubfg6.ybpnyqbznva6
State New
Headers show

Commit Message

Gerald Pfeifer Jan. 8, 2011, 4:54 p.m.
This further shortens cvs.html to the point where I hope it's
easier to consume for newcomers now.  Thanks again to Mingjie
Xing for making me focus on this.



Index: cvs.html
RCS file: /cvs/gcc/wwwdocs/htdocs/cvs.html,v
retrieving revision 1.218
diff -u -r1.218 cvs.html
--- cvs.html	6 Jan 2011 11:16:43 -0000	1.218
+++ cvs.html	8 Jan 2011 16:41:10 -0000
@@ -12,36 +12,24 @@ 
 <p>Our web pages and related scripts are available via our CVS
 repository.  You can also <a
 href="http://gcc.gnu.org/cgi-bin/cvsweb.cgi/wwwdocs/">browse them
-online</a> using cvsweb.</p>
 <h2>Using the CVS repository</h2>
 <p>Assuming you have both CVS 
 and SSH installed, you can check out the web pages as follows:</p>
-<ol type="i">
  <li>Set CVS_RSH in your environment to <code>ssh</code>.</li>
- <li>Set CVSROOT in your environment to 
-     <code>:pserver:cvs@gcc.gnu.org:/cvs/gcc</code>.&nbsp;
-     Alternately add 
-     <code>-d :pserver:cvs@gcc.gnu.org:/cvs/gcc</code>
-     immediately after <code>cvs</code> in the commands below.</li>
- <li><code>cvs -qz9 checkout -P wwwdocs</code></li>
+ <li><code>cvs -qz -d :ext:<i>username</i>@gcc.gnu.org:/cvs/gcc checkout
+-P wwwdocs</code> where <i>username</i> is your user name at gcc.gnu.org</li>
-<p>Patches should be marked with the tag [wwwdocs] in the subject line.</p>
-<hr />
-<h2><a name="write">Read-write CVS access</a></h2>
+<p>For anonymous access, use
+<code>-d :pserver:cvs@gcc.gnu.org:/cvs/gcc</code> instead.</p>
-<p>Check out things by setting environment variables as above and
-and issuing the command</p>
-cvs -z 9 -d :ext:<i>username</i>@gcc.gnu.org:/cvs/gcc co wwwdocs
+<p>Patches should be marked with the tag [wwwdocs] in the subject line.</p>
-<p>where <i>username</i> is your user name at gcc.gnu.org.</p>
 <hr />
 <h2><a name="checkin">Checking in a change</a></h2>
@@ -49,14 +37,10 @@ 
 <p>When you check in changes to our web pages, they will
 automatically be checked out into the web server's data area.</p>
-<p>The following is meant to provide a very quick overview of how to
-check in a change.  It is not meant to be a replacement for the CVS
-<p>In all the commands listed below, you can give an explicit list of
-filenames to the cvs command.  We recommend you list files explicitly
+<p>The following is meant to provide a very quick overview of how
+to check in a change.  We recommend you list files explicitly
 to avoid accidental checkins and prefer that each checkin be of a
-complete, single logical change, which may affect multiple files.</p>
+complete, single logical change.</p>
 <li>Sync your sources with the master repository via "<code>cvs
@@ -71,8 +55,7 @@ 
 <li>Use "<code>cvs commit</code>" to check in the patch.  You can enter
 the log message via the "<code>-m</code>" argument to commit, or wait for
-the editor window to appear and enter the log message in the editor
+the editor window to appear.</li>
 <li>Upon successfull checkin a message will be sent to the
 gcc-cvs-wwwdocs mailing list.</li>