public inbox for gcc-cvs-wwwdocs@sourceware.org help / color / mirror / Atom feed
From: gerald@gcc.gnu.org To: gcc-cvs-wwwdocs@gcc.gnu.org Subject: gcc-wwwdocs branch master updated. 848266eca465e98e1ad0bfb4dff37a8d0f073898 Date: Mon, 20 Jan 2020 19:34:00 -0000 [thread overview] Message-ID: <20200120193418.21745.qmail@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 848266eca465e98e1ad0bfb4dff37a8d0f073898 (commit) from 64481f8ceaefb7b6046bf6af43499797febccdef (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 848266eca465e98e1ad0bfb4dff37a8d0f073898 Author: Gerald Pfeifer <gerald@pfeifer.com> Date: Mon Jan 20 20:33:54 2020 +0100 You can also retrieve our sources using Git. diff --git a/htdocs/releases.html b/htdocs/releases.html index 30b777f4..1c8e87e2 100644 --- a/htdocs/releases.html +++ b/htdocs/releases.html @@ -22,8 +22,7 @@ As one option, there are <a href="https://gcc.gnu.org/install/binaries.html">pre-compiled binaries.</a> for various platforms.</p> -<p>You can also retrieve the current development sources -<a href="svn.html">using SVN</a>.</p> +<p>You can also retrieve our sources <a href="git.html">using Git</a>.</p> <h2 id="timeline">GCC Timeline</h2> ----------------------------------------------------------------------- Summary of changes: htdocs/releases.html | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) hooks/post-receive -- gcc-wwwdocs
reply other threads:[~2020-01-20 19:34 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=20200120193418.21745.qmail@sourceware.org \ --to=gerald@gcc.gnu.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).