diff mbox series

[wwwdocs] Replace use of <a name="..."> in all of bugs/

Message ID alpine.LSU.2.21.1808251234460.3241@anthias.pfeifer.com
State New
Headers show
Series [wwwdocs] Replace use of <a name="..."> in all of bugs/ | expand

Commit Message

Gerald Pfeifer Aug. 25, 2018, 10:54 a.m. UTC 
This is a necessary step on our move towards HTML 5.

Applied.

Gerald

Replace <a name="..."> by the use of it attributes in all of bugs/.

Comments

Gerald Pfeifer Aug. 25, 2018, 11 a.m. UTC | #1 
On Sat, 25 Aug 2018, Gerald Pfeifer wrote:
> Applied.

And here are two more that escaped my original search since the
<a name...></a> spanned two lines.

Applied as well.

Gerald

Index: bugs/index.html
===================================================================
RCS file: /cvs/gcc/wwwdocs/htdocs/bugs/index.html,v
retrieving revision 1.124
diff -u -r1.124 index.html
--- bugs/index.html	25 Aug 2018 10:35:47 -0000	1.124
+++ bugs/index.html	25 Aug 2018 10:59:42 -0000
@@ -219,8 +219,8 @@
 (If you use a mailing list for reporting, please include an
 "<code>[Ada]</code>" tag in the subject.)</p>
 
-<h2><a name="pch">Detailed bug reporting instructions when using a
-precompiled header</a></h2>
+<h2 id="pch">Detailed bug reporting instructions when using a precompiled
+header></h2>
 
 <p>If you're encountering a bug when using a precompiled header, the
 first thing to do is to delete the precompiled header, and try running
@@ -607,8 +607,8 @@
 and the scope operator.</p></dd>
 
 
-<dt><a name="cxx_rvalbind">Copy constructor access check while 
-initializing a reference.</a></dt>
+<dt id="cxx_rvalbind">Copy constructor access check while initializing a
+reference.</dt>
 
 <dd><p>Consider this code:</p>
diff mbox series

Patch

Index: index.html
===================================================================
RCS file: /cvs/gcc/wwwdocs/htdocs/bugs/index.html,v
retrieving revision 1.123
diff -u -r1.123 index.html
--- index.html	2 Jun 2018 21:16:11 -0000	1.123
+++ index.html	25 Aug 2018 10:25:49 -0000
@@ -37,7 +37,7 @@ 
 
 <hr />
 
-<h1><a name="report">Reporting Bugs</a></h1>
+<h1 id="report">Reporting Bugs</h1>
 
 <p>A good bug report, which is complete and self-contained, enables us
 to fix the bug.</p>
@@ -59,7 +59,7 @@ 
 <p>After this summary, you'll find detailed instructions that explain
 how to obtain some of the information requested in this summary.</p>
 
-<h3><a name="need">What we need</a></h3>
+<h3 id="need">What we need</h3>
 
 <p>Please include all of the following items, the first
 three of which can be obtained from the output of <code>gcc -v</code>:</p>
@@ -76,7 +76,7 @@ 
   a complete set of source files (see below).</li>
 </ul>
 
-<h3><a name="dontwant">What we do <strong>not</strong> want</a></h3>
+<h3 id="dontwant">What we do <strong>not</strong> want</h3>
 
 <ul>
   <li>A source file that <code>#include</code>s header files that are left
@@ -122,7 +122,7 @@ 
   dedicated to the discussion of the programming language</li>
 </ul>
 
-<h3><a name="where">Where to post it</a></h3>
+<h3 id="where">Where to post it</h3>
 
 <p>Please submit your bug report directly to the
 <a href="https://gcc.gnu.org/bugzilla/">GCC bug tracker</a>.
@@ -136,7 +136,7 @@ 
 this.  We apologize for the inconvenience.
 </p>
 
-<h2><a name="detailed">Detailed bug reporting instructions</a></h2>
+<h2 id="detailed">Detailed bug reporting instructions</h2>
 
 <p>Please refer to the <a href="#gnat">next section</a> when reporting
 bugs in GNAT, the Ada compiler, or to the <a href="#pch">one after
@@ -176,7 +176,7 @@ 
 the body of your bug report as plain text, even if needlessly
 duplicated as part of an archive.</p>
 
-<h2><a name="gnat">Detailed bug reporting instructions for GNAT</a></h2>
+<h2 id="gnat">Detailed bug reporting instructions for GNAT</h2>
 
 <p>See the <a href="#detailed">previous section</a> for bug reporting
 instructions for GCC language implementations other than Ada.</p>
@@ -245,7 +245,7 @@ 
 
 <hr />
 
-<h1><a name="known">Frequently Reported Bugs</a></h1>
+<h1 id="known">Frequently Reported Bugs</h1>
 
 <p>There are many reasons why a reported bug doesn't get fixed.
 It might be difficult to fix, or fixing it might break compatibility.
@@ -259,7 +259,7 @@ 
 
 <hr />
 
-<h1><a name="nonbugs">Non-bugs</a></h1>
+<h1 id="nonbugs">Non-bugs</h1>
 
 <p>The following are not actually bugs, but are reported often
 enough to warrant a mention here.</p>
@@ -274,7 +274,7 @@ 
 
 <hr />
 
-<h2><a name="nonbugs_general">General</a></h2>
+<h2 id="nonbugs_general">General</h2>
 
 <dl>
 <dt>Problems with floating point numbers - the
@@ -308,7 +308,7 @@ 
 
 <hr />
 
-<h2><a name="nonbugs_c">C</a></h2>
+<h2 id="nonbugs_c">C</h2>
 
 <dl>
 <dt>Increment/decrement operator (<code>++</code>/<code>--</code>) not
@@ -534,7 +534,7 @@ 
 
 <hr />
 
-<h2><a name="nonbugs_cxx">C++</a></h2>
+<h2 id="nonbugs_cxx">C++</h2>
 
 <dl>
 <dd><p>Most C++ compilers (G++ included) do not yet implement
@@ -657,7 +657,7 @@ 
 </dd>
 </dl>
 
-<h3><a name="upgrading">Common problems when upgrading the compiler</a></h3>
+<h3 id="upgrading">Common problems when upgrading the compiler</h3>
 
 <h4>ABI changes</h4>
 
Index: management.html
===================================================================
RCS file: /cvs/gcc/wwwdocs/htdocs/bugs/management.html,v
retrieving revision 1.36
diff -u -r1.36 management.html
--- management.html	2 Jun 2018 21:16:12 -0000	1.36
+++ management.html	25 Aug 2018 10:25:49 -0000
@@ -57,7 +57,7 @@ 
 <p>Bugzilla offers a number of different fields.  From a maintainer's
 perspective, these are the relevant ones and what their values mean:</p>
 
-<h3><a name="status">Status</a></h3>
+<h3 id="status">Status</h3>
 
 The status and resolution fields define and track the life cycle of a
 bug.  In addition to their <a
@@ -80,7 +80,7 @@ 
 
 </dl>
 
-<h3><a name="importance">Importance (Severity and Priority)</a></h3>
+<h3 id="importance">Importance (Severity and Priority)</h3>
 
 <p>The following two fields describe how serious a bug is from a user's
 perspective (Severity) and what Priority we assign to it in fixing it:</p>
@@ -157,7 +157,7 @@ 
 more important to fix in  GCC 7 than a regression that was introduced in GCC 5
 (and is still present in GCC 6 and 7).</p>
 
-<h3><a name="assigned_to">Assignee</a></h3>
+<h3 id="assigned_to">Assignee</h3>
 
 <p>This is the person in charge of resolving the bug.  Every time this
 field changes, the status changes to NEW to make it easy to see
@@ -178,7 +178,7 @@ 
 This makes sure that all NEW reports are really analyzed and are ready to
 be handed off to the people actually fixing bugs.</p>
 
-<p><a name="regression"><strong>Regressions</strong></a> should be explicitly
+<p id="regression"><strong>Regressions</strong> should be explicitly
 marked as such.  The summary line should read</p>
 
 <blockquote>