Patchwork [wwwdocs] patch: rename cvs.html to wwwdocs-cvs.html

login
register
mail settings
Submitter Quentin Neill
Date Jan. 20, 2011, 8:58 p.m.
Message ID <AANLkTin2T39FKs1-SsxKN9KKHKHgJYxWJACvdJzj+RGW@mail.gmail.com>
Download mbox | patch
Permalink /patch/79768/
State New
Headers show

Comments

Quentin Neill - Jan. 20, 2011, 8:58 p.m.
This patch repurposes cvs.html (from a wwwdocs access page to a
GCC/CVS page), cleans up links to cvs.html,
adds a new wwwdocs-cvs.html (with contents from old cvs.html)

Comments?

Patch

Index: about.html
===================================================================
RCS file: /cvs/gcc/wwwdocs/htdocs/about.html,v
retrieving revision 1.17
diff -u -r1.17 about.html
--- about.html	21 Sep 2006 14:17:36 -0000	1.17
+++ about.html	20 Jan 2011 20:56:29 -0000
@@ -25,7 +25,8 @@ 
 <a href="lists.html">mailing lists</a>.
 </p>
 
-<p>The web pages are under <a href="cvs.html">CVS control</a>. Changes
+<p>The wwwdocs repository containing the GCC web pages on this
+site are under <a href="wwwdocs-cvs.html">CVS control</a>.  Changes
 to the CVS repository immediately propagate to the web server and you
 can easily track any changes or contribute some of your own.
 </p>
Index: contribute.html
===================================================================
RCS file: /cvs/gcc/wwwdocs/htdocs/contribute.html,v
retrieving revision 1.77
diff -u -r1.77 contribute.html
--- contribute.html	10 Jul 2010 20:22:25 -0000	1.77
+++ contribute.html	20 Jan 2011 20:56:29 -0000
@@ -160,11 +160,11 @@ 
 
 <p>Changes to the web site must
 <a href="http://validator.w3.org/">validate</a> as XHTML 1.0
-Transitional.  The web pages as checked into CVS do not include
+Transitional.  The web pages versioned in source control do not include
 DOCTYPE declarations; they are automatically added when the web server
-checks out its copy.  To validate your changes, temporarily insert
-this header in place of the &lt;html&gt; tag, then use the "upload
-file" mode of the validator.</p>
+checks out its copy.  To validate your changes, temporarily insert this
+header in place of the &lt;html&gt; tag, then use the "upload file"
+mode of the validator.</p>
 
 <blockquote><pre>
 &lt;?xml version="1.0" encoding="ISO-8859-1"?&gt;
@@ -176,7 +176,9 @@ 
 
 <p>Please mark patches with the tag [wwwdocs] in the subject line.</p>
 
-<p>Web site sources are <a href="cvs.html">in CVS</a>.</p>
+<p>Note that web site sources are <a href="wwwdocs-cvs.html">in CVS</a>
+in contrast to the bulk of GCC source which is <a href="svn.html">in
+SVN</a>.</p>
 
 
 <h2><a name="patches">Submitting Patches</a></h2>
Index: cvs.html
===================================================================
RCS file: /cvs/gcc/wwwdocs/htdocs/cvs.html,v
retrieving revision 1.219
diff -u -r1.219 cvs.html
--- cvs.html	8 Jan 2011 16:50:20 -0000	1.219
+++ cvs.html	20 Jan 2011 20:56:29 -0000
@@ -1,76 +1,23 @@ 
 <html>
 
 <head>
-<meta name="description" content="Access to the GCC web pages via CVS" />
+<meta name="description" content="Access to the GCC sources via CVS" />
 <meta name="keywords" content="CVS, version control, GCC, source, public, repository" />
-<title>GCC: CVS access to our web pages</title>
+<title>GCC: CVS access to our source</title>
 </head>
 
 <body>
-<h1>GCC: CVS access to our web pages</h1>
+<h1>GCC: CVS access to the GCC source</h1>
+<p>On <a href=news.html#cvs_to_svn>October 26, 2005</a>
+GCC moved from CVS to <a href=svn.html>SVN</a> for revision control
+for almost all versioned files.   Most of the repository history
+was preserved in the switch.  
 
-<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>.</p>
+<p>Note that the GCC web pages and related scripts in the wwwdocs
+repository are still only available via <a href="wwwdocs-cvs.html">CVS</a>.
 
-<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>
- <li>Set CVS_RSH in your environment to <code>ssh</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>
-</ol>
-
-<p>For anonymous access, use
-<code>-d :pserver:cvs@gcc.gnu.org:/cvs/gcc</code> instead.</p>
-
-<p>Patches should be marked with the tag [wwwdocs] in the subject line.</p>
-
-
-<hr />
-<h2><a name="checkin">Checking in a change</a></h2>
-
-<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.  We recommend you list files explicitly
-to avoid accidental checkins and prefer that each checkin be of a
-complete, single logical change.</p>
-
-<ol>
-<li>Sync your sources with the master repository via "<code>cvs
-update</code>" before attempting a checkin; this will save you a little
-time if someone else has modified that file since the last time you
-synced your sources.  It will also identify any files in your local
-tree that you have modified.</li>
-
-<li>We recommend using "<code>cvs diff</code>" after applying a patch to a
-local tree.  Review the output to make sure that only the changes you
-wanted to check in will be checked in.</li>
-
-<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.</li>
-
-<li>Upon successfull checkin a message will be sent to the
-gcc-cvs-wwwdocs mailing list.</li>
-</ol>
-
-<hr />
-<h2><a name="system">The host system</a></h2>
-
-<p>The setup of the machine running the gcc.gnu.org site is also
-available, through
-<a href="http://sourceware.org/cgi-bin/cvsweb.cgi/?cvsroot=sourceware">
-cvsweb</a> and anonymous read-only CVS.  Use the same procedure
-as above, but use
-<code>:pserver:anoncvs@gcc.gnu.org:/cvs/sourceware</code> for the
-repository and <code>infra</code> for the module.</p>
+<p>For the latest details of how to access the GCC source files
+start on the main <a href=index.html>GCC page</a>.
 
 </body>
 </html>
Index: news.html
===================================================================
RCS file: /cvs/gcc/wwwdocs/htdocs/news.html,v
retrieving revision 1.128
diff -u -r1.128 news.html
--- news.html	18 Jan 2011 21:59:33 -0000	1.128
+++ news.html	20 Jan 2011 20:56:30 -0000
@@ -270,7 +270,7 @@ 
 <a href="gcc-3.4/">GCC 3.4.5</a> has been released.
 </dd>
 
-<dt><b>October 26, 2005</b></dt>
+<dt><a name="cvs_to_svn"><b>October 26, 2005</b></a></dt>
 <dd>
 GCC has moved from CVS to <a href="svn.html">SVN</a>
 for revision control.
Index: svn.html
===================================================================
RCS file: /cvs/gcc/wwwdocs/htdocs/svn.html,v
retrieving revision 1.158
diff -u -r1.158 svn.html
--- svn.html	19 Jan 2011 22:01:58 -0000	1.158
+++ svn.html	20 Jan 2011 20:56:30 -0000
@@ -18,7 +18,8 @@ 
 GCC that is in our repository.</p>
 
 <p>Our web pages are still maintained via CVS, and can be accessed
-using the directions for <a href="cvs.html">our CVS setup</a>.</p>
+using the directions on the <a href="wwwdocs-cvs.html">CVS wwwdocs access</a>
+page.</p>
 
 <p>In addition you can <a href="http://gcc.gnu.org/viewcvs/">browse
 our SVN history online</a>.</p>
Index: svnwrite.html
===================================================================
RCS file: /cvs/gcc/wwwdocs/htdocs/svnwrite.html,v
retrieving revision 1.19
diff -u -r1.19 svnwrite.html
--- svnwrite.html	21 Dec 2009 08:22:31 -0000	1.19
+++ svnwrite.html	20 Jan 2011 20:56:30 -0000
@@ -15,9 +15,9 @@ 
 significant developers. Maintainers are also encouraged to <a
   href="bugs/management.html">edit our bugs database</a>.
 
-Read/write access to the wwwdocs repository containing GCC
-www documents is still done using <a href="cvs.html">CVS</a>
-</p>
+<p>Read/write access to the wwwdocs repository (containing the
+GCC web pages on this site) is still done using <a
+href="wwwdocs-cvs.html">CVS</a>.</p>
 
 <hr />
 <h2>Contents</h2>
Index: wwwdocs-cvs.html
===================================================================
RCS file: wwwdocs-cvs.html
diff -N wwwdocs-cvs.html
--- /dev/null	1 Jan 1970 00:00:00 -0000
+++ wwwdocs-cvs.html	20 Jan 2011 20:56:30 -0000
@@ -0,0 +1,76 @@ 
+<html>
+
+<head>
+<meta name="description" content="Access to the GCC web pages via CVS" />
+<meta name="keywords" content="CVS, version control, GCC, source, public, repository" />
+<title>GCC: CVS access to our web pages</title>
+</head>
+
+<body>
+<h1>GCC: CVS access to our web pages</h1>
+
+<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>.</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>
+ <li>Set CVS_RSH in your environment to <code>ssh</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>
+</ol>
+
+<p>For anonymous access, use
+<code>-d :pserver:cvs@gcc.gnu.org:/cvs/gcc</code> instead.</p>
+
+<p>Patches should be marked with the tag [wwwdocs] in the subject line.</p>
+
+
+<hr />
+<h2><a name="checkin">Checking in a change</a></h2>
+
+<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.  We recommend you list files explicitly
+to avoid accidental checkins and prefer that each checkin be of a
+complete, single logical change.</p>
+
+<ol>
+<li>Sync your sources with the master repository via "<code>cvs
+update</code>" before attempting a checkin; this will save you a little
+time if someone else has modified that file since the last time you
+synced your sources.  It will also identify any files in your local
+tree that you have modified.</li>
+
+<li>We recommend using "<code>cvs diff</code>" after applying a patch to a
+local tree.  Review the output to make sure that only the changes you
+wanted to check in will be checked in.</li>
+
+<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.</li>
+
+<li>Upon successfull checkin a message will be sent to the
+gcc-cvs-wwwdocs mailing list.</li>
+</ol>
+
+<hr />
+<h2><a name="system">The host system</a></h2>
+
+<p>The setup of the machine running the gcc.gnu.org site is also
+available, through
+<a href="http://sourceware.org/cgi-bin/cvsweb.cgi/?cvsroot=sourceware">
+cvsweb</a> and anonymous read-only CVS.  Use the same procedure
+as above, but use
+<code>:pserver:anoncvs@gcc.gnu.org:/cvs/sourceware</code> for the
+repository and <code>infra</code> for the module.</p>
+
+</body>
+</html>
Index: java/build-snapshot.html
===================================================================
RCS file: /cvs/gcc/wwwdocs/htdocs/java/build-snapshot.html,v
retrieving revision 1.16
diff -u -r1.16 build-snapshot.html
--- java/build-snapshot.html	29 Jul 2002 16:50:01 -0000	1.16
+++ java/build-snapshot.html	20 Jan 2011 20:56:30 -0000
@@ -1,7 +1,7 @@ 
 <html>
 
 <head>
-<title>How to build GCJ/LIBGCJ from snapshots or cvs</title>
+<title>How to build GCJ/LIBGCJ from snapshots or from source</title>
 </head>
 
 <body>
@@ -9,7 +9,7 @@ 
 <table border="0" cellpadding="4" width="95%">
         <tr bgcolor="#b0d0ff"> 
           <th align="center"> 
-            <h2>Howto build and run libgcj/gcj snapshots or cvs</h2>
+            <h2>Howto build and run libgcj/gcj snapshots or from source</h2>
           </th>
         </tr>
 
@@ -17,7 +17,7 @@ 
 <tr bgcolor="#cccccc">
 <td>
 <pre>
-1. <a href="../snapshots.html">Get a GCC snapshot</a> or <a href="../cvs.html">obtain GCC via CVS</a>.
+1. Get GCC from a <a href="../snapshots.html">snapshot</a> or from <a href="../svn.html">source</a>.
 </pre>
 </td>
 </tr>
Index: projects/beginner.html
===================================================================
RCS file: /cvs/gcc/wwwdocs/htdocs/projects/beginner.html,v
retrieving revision 1.56
diff -u -r1.56 beginner.html
--- projects/beginner.html	20 Sep 2009 21:25:28 -0000	1.56
+++ projects/beginner.html	20 Jan 2011 20:56:30 -0000
@@ -22,7 +22,7 @@ 
 href="documentation.html">help with documentation</a> or with the <a
 href="http://gcc.gnu.org/bugzilla/">bug database</a>.</p>
 
-<p>We assume that you already know how to <a href="../cvs.html">get the
+<p>We assume that you already know how to <a href="../svn.html">get the
 latest sources</a>, configure and build the compiler, and run the test
 suite.  You should also familiarize yourself with the
 <a href="../contribute.html">requirements for contributions</a> to GCC.</p>
Index: projects/cfo.html
===================================================================
RCS file: /cvs/gcc/wwwdocs/htdocs/projects/cfo.html,v
retrieving revision 1.8
diff -u -r1.8 cfo.html
--- projects/cfo.html	30 Dec 2008 10:04:46 -0000	1.8
+++ projects/cfo.html	20 Jan 2011 20:56:30 -0000
@@ -29,7 +29,7 @@ 
 </p></dd>
 <dt>2004-11-16</dt>
 <dd><p>The branch is now open. Checkout the cfo-branch branch by following the
-instructions found in the <a href="../cvs.html">CVS documentation</a>.
+instructions found in the <a href="../svn.html">SVN access</a> page.
 </p></dd>
 </dl>
 
@@ -46,7 +46,7 @@ 
 <h2><a name="contributing">Contributing</a></h2>
 
 <p>Checkout the cfo-branch branch following the instructions found in the 
-<a href="../cvs.html">CVS documentation</a>.</p>
+<a href="../svn.html">SVN access</a> page.</p>
 
 <p>When posting to the development lists, please mark messages and patches with
 [cfo] in the subject. The usual contribution and testing rules apply. This
Index: projects/web.html
===================================================================
RCS file: /cvs/gcc/wwwdocs/htdocs/projects/web.html,v
retrieving revision 1.11
diff -u -r1.11 web.html
--- projects/web.html	30 Mar 2008 18:59:30 -0000	1.11
+++ projects/web.html	20 Jan 2011 20:56:30 -0000
@@ -8,8 +8,8 @@ 
 
 <h1>GCC: Web Pages</h1>
 
-<p>Our web pages are managed via CVS and can be accessed using the
-directions for <a href="../cvs.html">our CVS setup</a>.</p>
+<p>Our web pages are managed via SVN and can be accessed using the
+directions for <a href="../../svn.html">SVN access</a> documentation.</p>
 
 <h2>TODO</h2>
 
Index: projects/cxx-reflection/index.html
===================================================================
RCS file: /cvs/gcc/wwwdocs/htdocs/projects/cxx-reflection/index.html,v
retrieving revision 1.4
diff -u -r1.4 index.html
--- projects/cxx-reflection/index.html	25 Aug 2003 14:02:36 -0000	1.4
+++ projects/cxx-reflection/index.html	20 Jan 2011 20:56:30 -0000
@@ -22,8 +22,8 @@ 
 <h3>Contributing</h3>
 
 <p>Checkout the <code>cxx-reflection-branch</code> branch
-following the instructions found in the <a href="../../cvs.html">CVS
-documentation</a>.</p> 
+following the instructions found in the <a href="svn.html">SVN
+access</a> documentation.</p>  
 
 <p>When posting to the development lists, please mark messages and patches with
 <code>[cxx-reflection]</code> in the subject.  As this is a branch, and not
Index: projects/tree-ssa/index.html
===================================================================
RCS file: /cvs/gcc/wwwdocs/htdocs/projects/tree-ssa/index.html,v
retrieving revision 1.41
diff -u -r1.41 index.html
--- projects/tree-ssa/index.html	25 Apr 2009 22:58:23 -0000	1.41
+++ projects/tree-ssa/index.html	20 Jan 2011 20:56:30 -0000
@@ -79,7 +79,7 @@ 
 
 <p>Checkout the <code>tree-ssa-20020619-branch</code> branch
 following the instructions found in the <a
-href="../../cvs.html">CVS documentation</a>.</p>
+href="../../svn.html">SVN access</a> documentation.</p>
 
 <p>All contributions to the branch must also comply with the
 requirements detailed in the <a