public inbox for gcc-cvs-wwwdocs@sourceware.org
help / color / mirror / Atom feed
From: Jakub Jelinek <jakub@sourceware.org>
To: gcc-cvs-wwwdocs@gcc.gnu.org
Subject: gcc-wwwdocs branch master updated. e25fd8a37b818ee090f739fddd3e5df025f1e2f6
Date: Wed, 29 Sep 2021 11:52:42 +0000 (GMT)	[thread overview]
Message-ID: <20210929115242.4935F3858D28@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  e25fd8a37b818ee090f739fddd3e5df025f1e2f6 (commit)
      from  4405fd98dff55185e7ca3ca43e8ab108985d2bb2 (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 e25fd8a37b818ee090f739fddd3e5df025f1e2f6
Author: Jakub Jelinek <jakub@redhat.com>
Date:   Wed Sep 29 13:52:32 2021 +0200

    List 9.4 release in releases.html

diff --git a/htdocs/releases.html b/htdocs/releases.html
index 61ee1919..1cadd0a9 100644
--- a/htdocs/releases.html
+++ b/htdocs/releases.html
@@ -34,6 +34,7 @@ releases and an alternative view of the release history.</p>
 <table class="padding5">
 <tr><th>Release</th><th>Release date</th></tr>
 <tr><td><a href="gcc-11/">GCC 11.2</a></td>    <td>July 28, 2021</td></tr>
+<tr><td><a href="gcc-9/">GCC 9.4</a></td>     <td>June 1, 2021</td></tr>
 <tr><td><a href="gcc-8/">GCC 8.5</a></td>     <td>May 14, 2021</td></tr>
 <tr><td><a href="gcc-11/">GCC 11.1</a></td>    <td>April 27, 2021</td></tr>
 <tr><td><a href="gcc-10/">GCC 10.3</a></td>    <td>April 8, 2021</td></tr>

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

Summary of changes:
 htdocs/releases.html | 1 +
 1 file changed, 1 insertion(+)


hooks/post-receive
-- 
gcc-wwwdocs


                 reply	other threads:[~2021-09-29 11:52 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=20210929115242.4935F3858D28@sourceware.org \
    --to=jakub@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).