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. 9df88c1a84de5097556e5d421a2c2323b2d74d9d
Date: Wed, 21 Jul 2021 08:22:46 +0000 (GMT)	[thread overview]
Message-ID: <20210721082246.DB5B1389367D@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  9df88c1a84de5097556e5d421a2c2323b2d74d9d (commit)
      from  07ccda6044e0fb651be1c2ae5b7366411037c93d (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 9df88c1a84de5097556e5d421a2c2323b2d74d9d
Author: Richard Biener <rguenther@suse.de>
Date:   Wed Jul 21 10:22:27 2021 +0200

    Update GCC 11 branch status.

diff --git a/htdocs/index.html b/htdocs/index.html
index 7067a90a..76f2ff6a 100644
--- a/htdocs/index.html
+++ b/htdocs/index.html
@@ -159,9 +159,9 @@ More news? Let gerald@pfeifer.com know!
 </dt><dd>
   Status:
   <!--GCC 11 status below-->
-  <a href="https://gcc.gnu.org/pipermail/gcc/2021-July/236674.html">2021-07-06</a>
+  <a href="https://gcc.gnu.org/pipermail/gcc/2021-July/236836.html">2021-07-21</a>
   <!--GCC 11 status above-->
-  (regression fixes &amp; docs only).
+  (frozen for release).
   <div class="regress">
   <a
   href="https://gcc.gnu.org/bugzilla/buglist.cgi?query_format=advanced&amp;short_desc_type=regexp&amp;short_desc=%5C%5B(%5B%200-9.%2F%5D*%5B%20%2F%5D)*11%5B%20%2F%5D%5B%200-9.%2F%5D*%5BRr%5Degression%20*%5C%5D&amp;target_milestone=9.5&amp;target_milestone=10.4&amp;target_milestone=11.2&amp;known_to_fail_type=allwordssubstr&amp;known_to_work_type=allwordssubstr&amp;long_desc_type=allwordssubstr&amp;long_desc=&amp;bug_file_loc_type=allwordssubstr&amp;bug_file_loc=&amp;gcchost_type=allwordssubstr&amp;gcchost=&amp;gcctarget_type=allwordssubstr&amp;gcctarget=&amp;gccbuild_type=allwordssubstr&amp;gccbuild=&amp;keywords_type=allwords&amp;keywords=&amp;bug_status=UNCONFIRMED&amp;bug_status=NEW&amp;bug_status=ASSIGNED&amp;bug_status=SUSPENDED&amp;bug_status=WAITING&amp;bug_status=REOPENED&amp;priority=P1&amp;priority=P2&amp;priority=P3&amp;emailtype1=substring&amp;email1=&amp;emailtype2=substring&amp;email2=&amp;bugidtype=include&amp;bug_id=&amp;votes=&amp;chfieldfrom=&amp;chfieldto=Now&amp;chfieldvalue=&amp;cmdtype=doit&amp;order=Reuse+same+sort+as+last+time&amp;field0-0-0=noop&amp;type0-0-0=noop&amp;value0-0-0=">Serious

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

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


hooks/post-receive
-- 
gcc-wwwdocs


                 reply	other threads:[~2021-07-21  8:22 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=20210721082246.DB5B1389367D@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).