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. 0e7e3671ef866da3de44e2caa497bbd53808c7ef Date: Thu, 2 Dec 2021 18:46:52 +0000 (GMT) [thread overview] Message-ID: <20211202184652.566DD385841A@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 0e7e3671ef866da3de44e2caa497bbd53808c7ef (commit) from a8f744e6ae8ffec20e8b8fad46b79e44712068ae (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 0e7e3671ef866da3de44e2caa497bbd53808c7ef Author: Gerald Pfeifer <gerald@pfeifer.com> Date: Thu Dec 2 20:45:17 2021 +0200 git: Fix casing of GCC We've been referring to the project as GCC since GCC 2.95. diff --git a/htdocs/git.html b/htdocs/git.html index 493b5734..5fbd98bf 100644 --- a/htdocs/git.html +++ b/htdocs/git.html @@ -327,7 +327,7 @@ in Git.</p> by <a href="mailto:jason@gcc.gnu.org">Jason Merrill</a>.</dd> <dt>gccgo</dt> - <dd>This branch is for the Go front end to gcc. For more information + <dd>This branch is for the Go front end to GCC. For more information about the Go programming language, see <a href="https://go.dev/">go.dev</a>. The branch is maintained by Ian Lance Taylor. Patches should be ----------------------------------------------------------------------- Summary of changes: htdocs/git.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) hooks/post-receive -- gcc-wwwdocs
reply other threads:[~2021-12-02 18:46 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=20211202184652.566DD385841A@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).