public inbox for gcc-cvs-wwwdocs@sourceware.org
help / color / mirror / Atom feed
From: Richard Biener <rguenth@sourceware.org>
To: gcc-cvs-wwwdocs@gcc.gnu.org
Subject: gcc-wwwdocs branch master updated. 67c0749d0cce5a961d19c4a0a80f4750638959fa
Date: Fri,  7 Jul 2023 10:58:28 +0000 (GMT)	[thread overview]
Message-ID: <20230707105828.96617396E42C@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  67c0749d0cce5a961d19c4a0a80f4750638959fa (commit)
      from  81d1f4adbc7b619991dc3ae7b3b040b28f64fed8 (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 67c0749d0cce5a961d19c4a0a80f4750638959fa
Author: Richard Biener <rguenther@suse.de>
Date:   Fri Jul 7 12:58:11 2023 +0200

    note GCC 10 is no longer supported

diff --git a/htdocs/gcc-10/index.html b/htdocs/gcc-10/index.html
index e39a6381..a9547d18 100644
--- a/htdocs/gcc-10/index.html
+++ b/htdocs/gcc-10/index.html
@@ -11,6 +11,8 @@
 
 <h1>GCC 10 Release Series</h1>
 
+<p>(This release series is no longer supported.)</p>
+
 <p>July, 7, 2023</p>
 
 <p>The <a href="http://www.gnu.org">GNU project</a> and the GCC

-----------------------------------------------------------------------

Summary of changes:
 htdocs/gcc-10/index.html | 2 ++
 1 file changed, 2 insertions(+)


hooks/post-receive
-- 
gcc-wwwdocs

                 reply	other threads:[~2023-07-07 10:58 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=20230707105828.96617396E42C@sourceware.org \
    --to=rguenth@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: link
Be 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).