Re: [wwwdocs]: Patch for wwwdocs

[Gerald Pfeifer <gerald at pfeifer dot com>]

On Fri, 28 Oct 2005, Daniel Berlin wrote:
> I transformd the cvs session into an SVN one, and replaced the cvs docs
> so they only talk about wwwdocs.
>
> Other than that, it's just replacement of cvs info with equivalent svn
> info.

That's a nice example where SVN is better than CVS -- it would have 
allowed for doing much of this in the repository instead of removing
most from cvs.html and copying into a new svn.html. ;-)

Thanks for your work on the CVS->SVN conversion.  I think that will
really improve many things quite a bit!

> Okay?

Would you mind looking into the following minor comments?  Okay with
the appropriate changes.

Index: cvs.html
===================================================================
-<p>That way you can pick up any version (including releases) of GCC that
-is in our repository or our <a href="#wwwdocs">web pages</a>.</p>
+<p>That way you can pick up any version (including releases) 
+our <a href="#wwwdocs">web pages</a>.</p>

"of our"?

Index: style.mhtml
===================================================================
RCS file: /cvs/gcc/wwwdocs/htdocs/style.mhtml,v
retrieving revision 1.82
diff -u -p -r1.82 style.mhtml
--- style.mhtml	10 Jul 2005 21:09:24 -0000	1.82
+++ style.mhtml	28 Oct 2005 18:13:15 -0000
@@ -219,10 +219,9 @@
   </td></tr>
   <tr><td <nav-body-style> >
   <p>
-  <a href="<get-var BACKPATH>cvs.html">CVS read access</a><br />
+  <a href="<get-var BACKPATH>svn.html">CVS read access</a><br />
   <a href="<get-var BACKPATH>rsync.html">Rsync read access</a><br />
-  <a href="<get-var BACKPATH>cvsup.html">CVSup mirrors</a><br />
-  <a href="<get-var BACKPATH>cvswrite.html">CVS write access</a><br />
+  <a href="<get-var BACKPATH>svnwrite.html">CVS write access</a><br />
   </p>
   </td></tr>
   </table></td></tr>

I think we'll want to replace "CVS read access" with "SVN read access";
similarly for "CVS write access"?

Index: svn.html
===================================================================
+<p><b>In January 2004, these instructions were modified to reflect security
+changes implemented after an attack on the Free Software Foundation's
+site.</b></p>

Let's omit this.

+<p>Our SVN source tree contains a number of files that are generated

Let's make this "Our source tree", then we'll have less changes for
the next conversion, 2012. :-)

+<h2><a name="wwwdocs">Web pages</a></h2>
+
+<p>The web pages for the GCC project are also in the SVN repository
+and you can check them out, submit patches, etc just like you do for
+the compiler itself.</p>
+
+<p>Use <code>SVN co -P wwwdocs</code> to check out the web pages.</p>
+
+<p>Patches should be marked with the tag [wwwdocs] in the subject line.</p>

This is not yet true.

+<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://sources.redhat.com/cgi-bin/cvsweb.cgi/?cvsroot=sourceware";>
+cvsweb</a> and anonymous read-only CVS.  Use the same procedure
+as in <a href="cvs.html">CVS documentation</a> but use
+<code>:pserver:anoncvs@gcc.gnu.org:/cvs/sourceware</code> for the repository
+and <code>infra</code> for the module.</p>

And this should remain in cvs.html.

Once you committed that, I'll add redirects for the removed page, and
make one or two general changes, but I don't want to block you for these.

Gerald