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. a385664808c02ca56f86d76e66227c23db142c68 Date: Thu, 10 Feb 2022 07:54:33 +0000 (GMT) [thread overview] Message-ID: <20220210075433.350E13858D1E@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 a385664808c02ca56f86d76e66227c23db142c68 (commit) from 0ba89730c06d6078b1cc3d675d50e491ab73566f (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 a385664808c02ca56f86d76e66227c23db142c68 Author: Gerald Pfeifer <gerald@pfeifer.com> Date: Thu Feb 10 08:54:20 2022 +0100 gcc-4.7: Update link to Go 1 standard diff --git a/htdocs/gcc-4.7/changes.html b/htdocs/gcc-4.7/changes.html index 846946d6..c61106e5 100644 --- a/htdocs/gcc-4.7/changes.html +++ b/htdocs/gcc-4.7/changes.html @@ -691,7 +691,7 @@ well.</p></li> <h3 id="go">Go</h3> <ul> <li>GCC 4.7 implements - the <a href="https://golang.org/doc/go1">Go 1 + the <a href="https://go.dev/doc/go1">Go 1 language standard.</a> The library support in 4.7.0 is not quite complete, due to release timing. Release 4.7.1 includes complete support for Go 1. The Go library is from the Go 1.0.1 ----------------------------------------------------------------------- Summary of changes: htdocs/gcc-4.7/changes.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) hooks/post-receive -- gcc-wwwdocs
reply other threads:[~2022-02-10 7:54 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=20220210075433.350E13858D1E@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).