From: Gerald Pfeifer <gerald@pfeifer.com>
To: gcc-patches@gcc.gnu.org
Subject: [committed] wwwdocs: gcc-11: Switch from <a name> to using ids.
Date: Sat, 2 Apr 2022 15:31:31 +0200 (CEST) [thread overview]
Message-ID: <20220402133133.01F4433E5E@hamza.pair.com> (raw)
I - or rather the w3 validator :) - realized that the use of <a name>
is deprecated, so use id attributes instead.
Gerald
---
htdocs/gcc-11/changes.html | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/htdocs/gcc-11/changes.html b/htdocs/gcc-11/changes.html
index 8e6d4ec8..c9eb2295 100644
--- a/htdocs/gcc-11/changes.html
+++ b/htdocs/gcc-11/changes.html
@@ -1097,7 +1097,7 @@ is built as FAT libraries containing both 32 bit and 64 bit objects.</li>
</ul>
<!-- .................................................................. -->
-<h2><a name="11.1">GCC 11.1</a></h2>
+<h2 id="11.1">GCC 11.1</h2>
<p>This is the <a href="https://gcc.gnu.org/bugzilla/buglist.cgi?bug_status=RESOLVED&resolution=FIXED&target_milestone=11.0">list
of problem reports (PRs)</a> from GCC's bug tracking system that are
@@ -1106,7 +1106,7 @@ complete (that is, it is possible that some PRs that have been fixed
are not listed here).</p>
-<h2><a name="11.2">GCC 11.2</a></h2>
+<h2 id="11.2">GCC 11.2</h2>
<p>This is the <a href="https://gcc.gnu.org/bugzilla/buglist.cgi?bug_status=RESOLVED&resolution=FIXED&target_milestone=11.2">list
of problem reports (PRs)</a> from GCC's bug tracking system that are
@@ -1116,7 +1116,7 @@ are not listed here).</p>
<!-- .................................................................. -->
-<h2><a name="11.3">GCC 11.3</a></h2>
+<h2 id="11.3">GCC 11.3</h2>
<h3>Target Specific Changes</h3>
--
2.35.1
reply other threads:[~2022-04-02 13:31 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20220402133133.01F4433E5E@hamza.pair.com \
--to=gerald@pfeifer.com \
--cc=gcc-patches@gcc.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).