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. a17bfa6d7f838b0c6e1dab01f75313ed07ac867e
Date: Thu, 27 Jul 2023 09:08:56 +0000 (GMT)	[thread overview]
Message-ID: <20230727090856.89851385C6DD@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  a17bfa6d7f838b0c6e1dab01f75313ed07ac867e (commit)
      from  a1e45104b29ff3e6ca807f172e4886c6e9822b91 (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 a17bfa6d7f838b0c6e1dab01f75313ed07ac867e
Author: Jakub Jelinek <jakub@redhat.com>
Date:   Thu Jul 27 11:08:39 2023 +0200

    Update forgotten version number.

diff --git a/htdocs/index.html b/htdocs/index.html
index bf380d68..ec5ce2a6 100644
--- a/htdocs/index.html
+++ b/htdocs/index.html
@@ -128,7 +128,7 @@ More news? Let gerald@pfeifer.com know!
 <h2>Supported Releases</h2>
 <dl>
 
-<dt><span class="version"><a href="gcc-13/">GCC 13.1</a></span>
+<dt><span class="version"><a href="gcc-13/">GCC 13.2</a></span>
   (<a href="gcc-13/changes.html">changes</a>)
 </dt><dd>
   Status:

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

Summary of changes:
 htdocs/index.html | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)


hooks/post-receive
-- 
gcc-wwwdocs

                 reply	other threads:[~2023-07-27  9:08 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=20230727090856.89851385C6DD@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).