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. 84b60c36e51e1ca3a7e1a80ec70064c67c487fb7 Date: Fri, 17 Jan 2020 17:29:00 -0000 [thread overview] Message-ID: <20200117172941.18903.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 84b60c36e51e1ca3a7e1a80ec70064c67c487fb7 (commit) from 5667566dfa9eb624e5762b5d030f0a09fadf5e5b (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 84b60c36e51e1ca3a7e1a80ec70064c67c487fb7 Author: Gerald Pfeifer <gerald@pfeifer.com> Date: Fri Jan 17 18:28:24 2020 +0100 Reduce references to FTP for downloads. diff --git a/htdocs/gcc-2.95/branch.html b/htdocs/gcc-2.95/branch.html index 7ba3250f..03746846 100644 --- a/htdocs/gcc-2.95/branch.html +++ b/htdocs/gcc-2.95/branch.html @@ -29,7 +29,7 @@ situation you have three choices for handling your CVS tree.</p> <p>Considering that the primary focus of the developers is on the GCC 2.95 release, option #2 or #3 is recommended.</p> -<p>FTP snapshots will track the GCC 2.95 release only. After GCC 2.95 is +<p>Snapshots will track the GCC 2.95 release only. After GCC 2.95 is released, snapshots will return to tracking the mainline sources.</p> <hr /> diff --git a/htdocs/mirrors.html b/htdocs/mirrors.html index d8979b76..1917d04a 100644 --- a/htdocs/mirrors.html +++ b/htdocs/mirrors.html @@ -13,7 +13,7 @@ <p><a href="releases.html">Our releases</a> are available on the <a href="http://www.gnu.org/prep/ftp.html">GNU FTP server and its -mirrors</a>. The following sites mirror the gcc.gnu.org FTP site +mirrors</a>. The following sites mirror the gcc.gnu.org download site (Phoenix, Arizona, USA) directly:</p> <ul> diff --git a/htdocs/snapshots.html b/htdocs/snapshots.html index 7b15b0f5..3c491b00 100644 --- a/htdocs/snapshots.html +++ b/htdocs/snapshots.html @@ -14,7 +14,7 @@ <p>We recommend that you use <a href="svn.html">SVN to access our current development sources</a>.</p> -<p>We also make regular snapshots available for FTP download from our +<p>We also make regular snapshots available for download from our <a href="mirrors.html">mirror sites</a> about once a week. These snapshots are intended to give everyone access to work in progress. Any given snapshot may generate incorrect code or even fail to ----------------------------------------------------------------------- Summary of changes: htdocs/gcc-2.95/branch.html | 2 +- htdocs/mirrors.html | 2 +- htdocs/snapshots.html | 2 +- 3 files changed, 3 insertions(+), 3 deletions(-) hooks/post-receive -- gcc-wwwdocs
reply other threads:[~2020-01-17 17:29 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=20200117172941.18903.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).