public inbox for gcc-cvs-wwwdocs@sourceware.org help / color / mirror / Atom feed
From: Gerald Pfeifer <gerald@sourceware.org> To: gcc-cvs-wwwdocs@gcc.gnu.org Subject: gcc-wwwdocs branch master updated. 020a4fdb22f26524b50e50ff7ac1470cb3fe0c6b Date: Mon, 16 May 2022 20:52:43 +0000 (GMT) [thread overview] Message-ID: <20220516205243.DB24F3851C13@sourceware.org> (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 020a4fdb22f26524b50e50ff7ac1470cb3fe0c6b (commit) from 3467751f053f006024489877a8b2bb5823d186cd (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 020a4fdb22f26524b50e50ff7ac1470cb3fe0c6b Author: Gerald Pfeifer <gerald@pfeifer.com> Date: Mon May 16 22:52:01 2022 +0200 gcc-13: Use HTML id instead of <a name=...> diff --git a/htdocs/gcc-13/changes.html b/htdocs/gcc-13/changes.html index f21b546b..a1b64df3 100644 --- a/htdocs/gcc-13/changes.html +++ b/htdocs/gcc-13/changes.html @@ -141,7 +141,7 @@ a work-in-progress.</p> <!-- <h3 id="uninitialized">Eliminating uninitialized variables</h3> --> <!-- .................................................................. --> -<!-- <h2><a name="13.1">GCC 13.1</a></h2> --> +<!-- <h2 id="13.1">GCC 13.1</h2> --> </body> </html> ----------------------------------------------------------------------- Summary of changes: htdocs/gcc-13/changes.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) hooks/post-receive -- gcc-wwwdocs
reply other threads:[~2022-05-16 20:52 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=20220516205243.DB24F3851C13@sourceware.org \ --to=gerald@sourceware.org \ --cc=gcc-cvs-wwwdocs@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: linkBe 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).