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. 82f1a66ddecdbfba768e9841ba2c17e15b0bb4d0 Date: Tue, 30 Nov 2021 21:08:31 +0000 (GMT) [thread overview] Message-ID: <20211130210831.AA48E3858D3C@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 82f1a66ddecdbfba768e9841ba2c17e15b0bb4d0 (commit) from 2ae2192e50b84c18a307c9889f533dd0f8627eac (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 82f1a66ddecdbfba768e9841ba2c17e15b0bb4d0 Author: Gerald Pfeifer <gerald@pfeifer.com> Date: Tue Nov 30 23:08:08 2021 +0200 gcc-4.7: Update reference to Go 1 language standard diff --git a/htdocs/gcc-4.7/changes.html b/htdocs/gcc-4.7/changes.html index 21294cc3..846946d6 100644 --- a/htdocs/gcc-4.7/changes.html +++ b/htdocs/gcc-4.7/changes.html @@ -1017,8 +1017,7 @@ complete (that is, it is possible that some PRs that have been fixed are not listed here).</p> <p>The Go front end in the 4.7.1 release fully supports -the <a href="https://golang.org/doc/go1">Go 1 language -standard.</a></p> +the <a href="https://go.dev/doc/go1">Go 1 language standard.</a></p> <h2 id="GCC4.7.2">GCC 4.7.2</h2> ----------------------------------------------------------------------- Summary of changes: htdocs/gcc-4.7/changes.html | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) hooks/post-receive -- gcc-wwwdocs
reply other threads:[~2021-11-30 21:08 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=20211130210831.AA48E3858D3C@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).