[wwwdocs] Adjust to move from bugs.html to bugs/

[Gerald Pfeifer]

...for the main page navigation and the bugs/minimize.html patch.

(This avoids a redirect from the server and increases concistency; the
links where never broken and still work.)

Installed.

Gerald

Index: style.mhtml
===================================================================
RCS file: /cvs/gcc/wwwdocs/htdocs/style.mhtml,v
retrieving revision 1.102
diff -u -3 -p -r1.102 style.mhtml
--- style.mhtml 9 Jul 2009 14:30:10 -0000 1.102
+++ style.mhtml 3 Nov 2009 22:19:21 -0000
@@ -236,8 +236,8 @@
   <b>Bugs</b>
   </td></tr>
   <tr><td <nav-body-style> >
-  <a href="<get-var BACKPATH>bugs.html#known">Known bugs</a><br />
-  <a href="<get-var BACKPATH>bugs.html">How to report</a><br />
+  <a href="<get-var BACKPATH>bugs/#known">Known bugs</a><br />
+  <a href="<get-var BACKPATH>bugs/">How to report</a><br />
   <a href="http://gcc.gnu.org/bugzilla/">Bug database</a><br />
   · <a href="<get-var BACKPATH>bugs/management.html">Management</a>
   </td></tr>
Index: bugs/minimize.html
===================================================================
RCS file: /cvs/gcc/wwwdocs/htdocs/bugs/minimize.html,v
retrieving revision 1.4
diff -u -3 -p -r1.4 minimize.html
--- bugs/minimize.html 9 May 2003 11:18:47 -0000 1.4
+++ bugs/minimize.html 3 Nov 2009 22:19:21 -0000
@@ -10,7 +10,7 @@
 
 <p>In order for a GCC developer to fix a bug, the bug must be
 reproducible by means of a self-contained test case. Our
-<a href="../bugs.html">bug reporting instructions</a>
+<a href="./">bug reporting instructions</a>
 ask that a bug report include the preprocessed version of the file that
 triggers the bug.  Often this file is very large; there are several
 reasons for making it as small as possible:</p>

[Gerald Pfeifer]

On Tue, 3 Nov 2009, Gerald Pfeifer wrote:
> ...for the main page navigation and the bugs/minimize.html patch.
>
> (This avoids a redirect from the server and increases concistency; the
> links where never broken and still work.)

And this handles the gcc-X.Y/changes.html pages.

Installed.

Gerald
Index: gcc-3.4/changes.html
===================================================================
RCS file: /cvs/gcc/wwwdocs/htdocs/gcc-3.4/changes.html,v
retrieving revision 1.154
diff -u -3 -p -r1.154 changes.html
--- gcc-3.4/changes.html 3 May 2008 12:28:02 -0000 1.154
+++ gcc-3.4/changes.html 8 Nov 2009 17:42:39 -0000
@@ -613,7 +613,7 @@ and not your code, that is broken.</em><
 
  <p>This might be surprising at first sight, especially since most
  popular compilers do not correctly implement this rule
- (<a href="../bugs.html#cxx_rvalbind">further details</a>).</p></li>
+ (<a href="../bugs/#cxx_rvalbind">further details</a>).</p></li>
 
  <li>When forming a pointer to member or a pointer to member function,
  access checks for class visibility (public, protected, private)
Index: gcc-4.2/changes.html
===================================================================
RCS file: /cvs/gcc/wwwdocs/htdocs/gcc-4.2/changes.html,v
retrieving revision 1.37
diff -u -3 -p -r1.37 changes.html
--- gcc-4.2/changes.html 25 Jan 2009 20:57:09 -0000 1.37
+++ gcc-4.2/changes.html 8 Nov 2009 17:42:39 -0000
@@ -75,8 +75,7 @@
     <code>-fno-unit-at-a-time</code> option will be removed in some
     future version of GCC.  If you know of a case which requires
     <code>-fno-unit-at-a-time</code> which is not fixed by
-    <code>-fno-toplevel-reorder</code>, please <a
-    href="http://gcc.gnu.org/bugs.html">open a bug report</a>.</li>
+    <code>-fno-toplevel-reorder</code>, please open a bug report.</li>
 
 </ul>
 

[Gerald Pfeifer]

In this case by avoiding the link altogether; installed.

Gerald

Index: projects/index.html
===================================================================
RCS file: /cvs/gcc/wwwdocs/htdocs/projects/index.html,v
retrieving revision 1.63
diff -u -3 -p -r1.63 index.html
--- projects/index.html 21 Jan 2006 20:19:20 -0000 1.63
+++ projects/index.html 17 Nov 2009 22:37:43 -0000
@@ -109,8 +109,8 @@ now have a way to understand this.</p>
 (the file hadn't changed since GCC 2.0), but some might be.  Someone
 should go through it, identifying what is and isn't relevant, adding
 anything applicable to current GCC (and describing a bug) to our
-<a href="../bugs.html">bug-tracking system</a> and sending patches to
-gcc-patches to remove such analysed entries from the list.</p>
+bug-tracking system and/or updating this patch to remove such analysed
+entries from the list.</p>
 
 <ol>
   <li value="110">Possible special combination pattern: If the two

[Gerald Pfeifer]

On Tue, 3 Nov 2009, Gerald Pfeifer wrote:
> ...for the main page navigation and the bugs/minimize.html patch.

And this is for the FAQ.  Installed.

Gerald

Index: faq.html
===================================================================
RCS file: /cvs/gcc/wwwdocs/htdocs/faq.html,v
retrieving revision 1.207
diff -u -3 -p -r1.207 faq.html
--- faq.html 1 Jan 2009 20:15:25 -0000 1.207
+++ faq.html 17 Nov 2009 20:50:42 -0000
@@ -85,7 +85,7 @@ disadvantages.</p>
     benefits of your changes, your code may or may not ever make it
     into an official release of GCC.</li>
 
-<li><a href="bugs.html">Report the problem to the GCC bug tracking system</a>
+<li><a href="bugs/">Report the problem to the GCC bug tracking system</a>
     and hope that someone will be kind
     enough to fix it for you.  While this is certainly possible, and
     often happens, there is no guarantee that it will.  You should

[Gerald Pfeifer]

And this is one final adjustment.  Installed.

Gerald

Index: gcc-4.4/porting_to.html
===================================================================
RCS file: /cvs/gcc/wwwdocs/htdocs/gcc-4.4/porting_to.html,v
retrieving revision 1.5
diff -u -3 -p -r1.5 porting_to.html
--- gcc-4.4/porting_to.html 18 Apr 2009 21:11:37 -0000 1.5
+++ gcc-4.4/porting_to.html 3 Dec 2009 08:28:22 -0000
@@ -96,10 +96,10 @@ This can be temporarily worked around by
 using <code>-fno-strict-aliasing </code> or by ignoring this class of
 warning via <code>-Wno-strict-aliasing</code>. To fix, access the
 structure from pointers of an equivalent type, use a union, use
-memcpy, or (if using C++) use placement new. See the section titled "Casting
-does not work as expected when optimization is turned on" on the GCC bug
-reporting documentation <a href="http://gcc.gnu.org/bugs.html">page</a> for more
-information.
+memcpy, or (if using C++) use placement new. See the section titled
+"Casting does not work as expected when optimization is turned
+on" on <a href="http://gcc.gnu.org/bugs/">bug reporting
+documentation page</a> for more information.
 </p>
 
 <h3>C++ language issues</h3>