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. b373a82c4fa2bd6eee719fabadde634fed3bb890 Date: Mon, 20 Jan 2020 10:37:00 -0000 [thread overview] Message-ID: <20200120103754.131010.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 b373a82c4fa2bd6eee719fabadde634fed3bb890 (commit) from e48a9f9ec49f5e3e50e5e614bcfecb9543747441 (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 b373a82c4fa2bd6eee719fabadde634fed3bb890 Author: Gerald Pfeifer <gerald@pfeifer.com> Date: Mon Jan 20 11:36:41 2020 +0100 Polish our page on releases a bit. We now require a C++ compiler to bootstrap. Short some text here and there. diff --git a/htdocs/releases.html b/htdocs/releases.html index c7a9bf1c..30b777f4 100644 --- a/htdocs/releases.html +++ b/htdocs/releases.html @@ -13,15 +13,14 @@ <h2 id="download">Download</h2> -<p>Source code for GCC releases may be downloaded from our +<p>GCC releases may be downloaded from our <a href="mirrors.html">mirror sites</a>.</p> -<p><em>Important: because these are source releases, they will be -of little use to you if you do not already have a C compiler on your -machine.</em> If you don't already have a compiler, you need pre-compiled -binaries. -Our <a href="https://gcc.gnu.org/install/binaries.html">binaries page</a> -has references to pre-compiled binaries for various platforms.</p> +<p><em>Important: these are source releases, so will be of little +use if you do not already have a C++ compiler installed.</em> +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> @@ -29,12 +28,9 @@ has references to pre-compiled binaries for various platforms.</p> <h2 id="timeline">GCC Timeline</h2> -<p>The table is sorted by date. Note that starting with version 3.3.4, -we provide bug releases for older release branches for those users -who require a very high degree of stability.</p> - -<p>Please refer to our <a href="develop.html#timeline">development plan</a> -for future releases, and an alternative view of the release history.</p> +<p>The table is sorted by date. Please refer to our +<a href="develop.html#timeline">development plan</a> for future +releases and an alternative view of the release history.</p> <table class="padding5"> <tr><th>Release</th><th>Release date</th></tr> ----------------------------------------------------------------------- Summary of changes: htdocs/releases.html | 22 +++++++++------------- 1 file changed, 9 insertions(+), 13 deletions(-) hooks/post-receive -- gcc-wwwdocs
reply other threads:[~2020-01-20 10:37 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=20200120103754.131010.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).