public inbox for
help / color / mirror / Atom feed
From: Gerald Pfeifer <>
Subject: gcc-wwwdocs branch master updated. 3467751f053f006024489877a8b2bb5823d186cd
Date: Sat, 14 May 2022 06:44:30 +0000 (GMT)	[thread overview]
Message-ID: <> (raw)

This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "gcc-wwwdocs".

The branch, master has been updated
       via  3467751f053f006024489877a8b2bb5823d186cd (commit)
      from  01a1afc13afd0e2b981262b0a1bf9ba1d7d19f79 (commit)

Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.

- Log -----------------------------------------------------------------
commit 3467751f053f006024489877a8b2bb5823d186cd
Author: Gerald Pfeifer <>
Date:   Sat May 14 08:43:18 2022 +0200

    gcc-12: Use HTML id instead of <a name>
    <a name> here came in via e9d81288aaae7626d7b511e0f84cba3e72f47b52
    which is deprecated. Simply use an id instead.

diff --git a/htdocs/gcc-12/changes.html b/htdocs/gcc-12/changes.html
index a32f1d53..0eae78ff 100644
--- a/htdocs/gcc-12/changes.html
+++ b/htdocs/gcc-12/changes.html
@@ -1020,7 +1020,7 @@ function Multiply (S1, S2 : Sign) return Sign is
 <!-- .................................................................. -->
-<h2><a name="12.1">GCC 12.1</a></h2>
+<h2 id="12.1">GCC 12.1</h2>
 <p>This is the <a href=";resolution=FIXED&amp;target_milestone=12.0">list
 of problem reports (PRs)</a> from GCC's bug tracking system that are


Summary of changes:
 htdocs/gcc-12/changes.html | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)


                 reply	other threads:[~2022-05-14  6:44 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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \

* 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).