Enclosed is a patch modifying three broken links, on three separate
pages. I also added some indications to about.html on how to submit a
patch for the web site for those who do not have commit access, which is
precisely what I have been instructed to do (so now it becomes
documented).
See <http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59184> for more
information.
All the best,
Philippe Baril Lecavalier
Index: projects/beginner.html
===================================================================
RCS file: /cvs/gcc/wwwdocs/htdocs/projects/beginner.html,v
retrieving revision 1.57
diff -u -r1.57 beginner.html
--- projects/beginner.html 29 Dec 2012 00:24:56 -0000 1.57
+++ projects/beginner.html 20 Nov 2013 04:55:23 -0000
@@ -32,7 +32,7 @@
<a href="http://gcc.gnu.org/onlinedocs/gccint/RTL.html">RTL</a>.
It may help to understand the higher-level <code>tree</code> structure as
well. Unfortunately, for this we only have an <a
-href="http://gcc.gnu.org/onlinedocs/gccint/Trees.html">incomplete, C/C++ specific manual</a>.</p>
+href="http://gcc.gnu.org/onlinedocs/gccint/GENERIC.html">incomplete, C/C++ specific manual</a>.</p>
<p>Remember to <a href="../contributewhy.html">keep other developers
informed</a> of any substantial projects you intend to work on.</p>
Index: projects/documentation.html
===================================================================
RCS file: /cvs/gcc/wwwdocs/htdocs/projects/documentation.html,v
retrieving revision 1.5
diff -u -r1.5 documentation.html
--- projects/documentation.html 19 Sep 2007 22:40:29 -0000 1.5
+++ projects/documentation.html 20 Nov 2013 04:55:23 -0000
@@ -56,7 +56,7 @@
<p>We've got quite a bit of this but it is scattered all over the
place. It belongs in the official manual. There is a <a
-href="http://gcc.gnu.org/onlinedocs/gccint/Trees.html">C/C++ specific manual</a>,
+href="http://gcc.gnu.org/onlinedocs/gccint/GENERIC.html">C/C++ specific manual</a>,
which is incomplete, though. The file
<code>gcc/LANGUAGES</code> contains incomplete and outdated information
about changes made in not so recent years to the <code>tree</code>
Index: readings.html
===================================================================
RCS file: /cvs/gcc/wwwdocs/htdocs/readings.html,v
retrieving revision 1.233
diff -u -r1.233 readings.html
--- readings.html 31 Oct 2013 18:03:28 -0000 1.233
+++ readings.html 20 Nov 2013 04:55:23 -0000
@@ -401,7 +401,7 @@
<h3>Objective-C Information</h3>
<ul>
- <li><a href="http://developer.apple.com/documentation/Cocoa/Conceptual/ObjectiveC/">
+ <li><a href="https://developer.apple.com/library/mac/documentation/cocoa/conceptual/ProgrammingWithObjectiveC/Introduction/Introduction.html">
Objective-C Language Description</a> (Apple Computer)</li>
</ul>
Index: about.html
===================================================================
RCS file: /cvs/gcc/wwwdocs/htdocs/about.html,v
retrieving revision 1.19
diff -u -r1.19 about.html
--- about.html 18 Aug 2013 20:38:58 -0000 1.19
+++ about.html 20 Nov 2013 04:55:23 -0000
@@ -69,6 +69,24 @@
list.</li>
</ol>
+<p>If you do not have commit access, please send an email to <a
+ href="mailto:gcc-patches@gcc.gnu.org">gcc-patches@gcc.gnu.org</a>
+and CC <a href="mailto:ger...@pfeifer.com">ger...@pfeifer.com</a>,
+with the following:</p>
+
+<ul>
+<li> Secify <code>[wwwwdocs]</code> in the subject header.</li>
+
+<li> Description of your patch and list of modified files.</li>
+
+<li> Mention the fact that you do not have commit access (why you do
+this).</li>
+
+<li> Link to <a href="http://gcc.gnu.org/bugzilla/">bugzilla</a>
+issue, if applicable.</li>
+
+<li> Your patch (from <code>cvs diff</code>) as an attachment.</li>
+</ul>
<h2 id="system">The host system</h2>