Remove a couple of links. Make a couple of links relative. Consistently use bug tracker to refer to our Bugzilla system.
As a side effect, this further reduces the number of http links to gcc.gnu.org. Applied. Gerald Index: gcc-3.3/changes.html =================================================================== RCS file: /cvs/gcc/wwwdocs/htdocs/gcc-3.3/changes.html,v retrieving revision 1.61 diff -u -r1.61 changes.html --- gcc-3.3/changes.html 28 Jun 2014 20:35:50 -0000 1.61 +++ gcc-3.3/changes.html 28 Jun 2014 22:41:27 -0000 @@ -916,8 +916,7 @@ <h3>Bug Fixes</h3> -<p>This section lists the problem reports (PRs) from -<a href="http://gcc.gnu.org/bugzilla/">GCC's bug tracking system</a> +<p>This section lists the problem reports (PRs) from GCC's bug tracker that are known to be fixed in the 3.3.2 release. This list might not be complete (that is, it is possible that some PRs that have been fixed are not listed here).</p> @@ -1058,8 +1057,7 @@ <h3>Bug Fixes</h3> -<p>This section lists the problem reports (PRs) from -<a href="http://gcc.gnu.org/bugzilla/">GCC's bug tracking system</a> +<p>This section lists the problem reports (PRs) from GCC's bug tracker that are known to be fixed in the 3.3.3 release. This list might not be complete (that is, it is possible that some PRs that have been fixed are not listed here).</p> Index: gcc-4.0/changes.html =================================================================== RCS file: /cvs/gcc/wwwdocs/htdocs/gcc-4.0/changes.html,v retrieving revision 1.65 diff -u -r1.65 changes.html --- gcc-4.0/changes.html 28 Jun 2014 20:35:51 -0000 1.65 +++ gcc-4.0/changes.html 28 Jun 2014 22:41:27 -0000 @@ -346,7 +346,7 @@ <h3>Fortran</h3> <ul> - <li>A new <a href="http://gcc.gnu.org/fortran/">Fortran</a> front end + <li>A new <a href="../fortran/">Fortran</a> front end has replaced the aging GNU Fortran 77 front end. The new front end supports Fortran 90 and Fortran 95. It may not yet be as stable as the old Fortran front end. Index: gcc-4.3/changes.html =================================================================== RCS file: /cvs/gcc/wwwdocs/htdocs/gcc-4.3/changes.html,v retrieving revision 1.129 diff -u -r1.129 changes.html --- gcc-4.3/changes.html 28 Jun 2014 20:35:51 -0000 1.129 +++ gcc-4.3/changes.html 28 Jun 2014 22:41:28 -0000 @@ -163,8 +163,7 @@ platforms and <code>-msse/-msse2</code> for i?86 and x86_64.</li> <li>More information on porting to GCC 4.3 from previous versions - of GCC can be found in - the <a href="http://gcc.gnu.org/gcc-4.3/porting_to.html">porting + of GCC can be found in the <a href="porting_to.html">porting guide</a> for this release.</li> </ul> Index: gcc-4.3/porting_to.html =================================================================== RCS file: /cvs/gcc/wwwdocs/htdocs/gcc-4.3/porting_to.html,v retrieving revision 1.11 diff -u -r1.11 porting_to.html --- gcc-4.3/porting_to.html 28 Jun 2014 07:45:13 -0000 1.11 +++ gcc-4.3/porting_to.html 28 Jun 2014 22:41:28 -0000 @@ -9,8 +9,7 @@ <p> The GCC 4.3 release series differs from previous GCC releases in more -than the usual list -of <a href="http://gcc.gnu.org/gcc-4.3/changes.html">new +than the usual list of <a href="changes.html">new features</a>. Some of these changes are a result of bug fixing, and some old behaviors have been intentionally changed in order to support new standards, or relaxed in standards-conforming ways to facilitate Index: gcc-4.4/changes.html =================================================================== RCS file: /cvs/gcc/wwwdocs/htdocs/gcc-4.4/changes.html,v retrieving revision 1.87 diff -u -r1.87 changes.html --- gcc-4.4/changes.html 28 Jun 2014 20:35:51 -0000 1.87 +++ gcc-4.4/changes.html 28 Jun 2014 22:41:28 -0000 @@ -121,8 +121,7 @@ are issued, then GCC warns about the unknown options.</li> <li>More information on porting to GCC 4.4 from previous versions - of GCC can be found in - the <a href="http://gcc.gnu.org/gcc-4.4/porting_to.html">porting + of GCC can be found in the <a href="porting_to.html">porting guide</a> for this release.</li> </ul> Index: gcc-4.4/porting_to.html =================================================================== RCS file: /cvs/gcc/wwwdocs/htdocs/gcc-4.4/porting_to.html,v retrieving revision 1.8 diff -u -r1.8 porting_to.html --- gcc-4.4/porting_to.html 27 Jun 2014 18:53:31 -0000 1.8 +++ gcc-4.4/porting_to.html 28 Jun 2014 22:41:28 -0000 @@ -9,8 +9,7 @@ <p> The GCC 4.4 release series differs from previous GCC releases in more -than the usual list -of <a href="http://gcc.gnu.org/gcc-4.4/changes.html">new +than the usual list of <a href="changes.html">new features</a>. Some of these changes are a result of bug fixing, and some old behaviors have been intentionally changed in order to support new standards, or relaxed in standards-conforming ways to facilitate Index: gcc-4.6/changes.html =================================================================== RCS file: /cvs/gcc/wwwdocs/htdocs/gcc-4.6/changes.html,v retrieving revision 1.150 diff -u -r1.150 changes.html --- gcc-4.6/changes.html 28 Jun 2014 20:35:51 -0000 1.150 +++ gcc-4.6/changes.html 28 Jun 2014 22:41:29 -0000 @@ -139,8 +139,7 @@ in GCC 4.5</a>.</li> <li>More information on porting to GCC 4.6 from previous versions - of GCC can be found in - the <a href="http://gcc.gnu.org/gcc-4.6/porting_to.html">porting + of GCC can be found in the <a href="porting_to.html">porting guide</a> for this release.</li> </ul> Index: gcc-4.6/porting_to.html =================================================================== RCS file: /cvs/gcc/wwwdocs/htdocs/gcc-4.6/porting_to.html,v retrieving revision 1.6 diff -u -r1.6 porting_to.html --- gcc-4.6/porting_to.html 19 Nov 2011 16:59:22 -0000 1.6 +++ gcc-4.6/porting_to.html 28 Jun 2014 22:41:29 -0000 @@ -9,8 +9,7 @@ <p> The GCC 4.6 release series differs from previous GCC releases in more -than the usual list of -<a href="http://gcc.gnu.org/gcc-4.6/changes.html">changes</a>. Some of +than the usual list of <a href="changes.html">changes</a>. Some of these are a result of bug fixing, and some old behaviors have been intentionally changed in order to support new standards, or relaxed in standards-conforming ways to facilitate compilation or runtime