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. e2dd56b3b9ae4d9bad75e02dfe307ecf931701af Date: Thu, 21 Apr 2022 09:09:27 +0000 (GMT) [thread overview] Message-ID: <20220421090927.6A8413856DD5@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 e2dd56b3b9ae4d9bad75e02dfe307ecf931701af (commit) from f7758e29e25de4870e272d41ad1ce8e054bf8595 (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 e2dd56b3b9ae4d9bad75e02dfe307ecf931701af Author: Richard Biener <rguenther@suse.de> Date: Thu Apr 21 11:09:04 2022 +0200 Update GCC 11 status, add 11.3 news item. diff --git a/htdocs/index.html b/htdocs/index.html index b8d81f09..a683106a 100644 --- a/htdocs/index.html +++ b/htdocs/index.html @@ -55,6 +55,10 @@ mission statement</a>.</p> <h2 id="news">News</h2> <dl> +<dt><span><a href="gcc-11/">GCC 11.3</a> released</span> + <span class="date">[2022-04-21]</span></dt> + <dd></dd> + <dt><span><a href="https://gcc.gnu.org/wiki/linuxplumbers2021">GNU Tools @ Linux Plumbers Conference 2021</a></span> <span class="date">[2021-09-15]</span></dt> <dd>Will be held online, September 20-24 2021</dd> @@ -163,14 +167,14 @@ More news? Let gerald@pfeifer.com know! <h2>Supported Releases</h2> <dl> -<dt><span class="version"><a href="gcc-11/">GCC 11.2</a></span> +<dt><span class="version"><a href="gcc-11/">GCC 11.3</a></span> (<a href="gcc-11/changes.html">changes</a>) </dt><dd> Status: <!--GCC 11 status below--> - <a href="https://gcc.gnu.org/pipermail/gcc/2022-April/238547.html">2022-04-13</a> + <a href="https://gcc.gnu.org/pipermail/gcc/2022-April/238572.html">2022-04-21</a> <!--GCC 11 status above--> - (frozen for release). + (regression fixes & docs only). <div class="regress"> <a href="https://gcc.gnu.org/bugzilla/buglist.cgi?query_format=advanced&short_desc_type=regexp&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&target_milestone=9.5&target_milestone=10.4&target_milestone=11.4&known_to_fail_type=allwordssubstr&known_to_work_type=allwordssubstr&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&gcchost_type=allwordssubstr&gcchost=&gcctarget_type=allwordssubstr&gcctarget=&gccbuild_type=allwordssubstr&gccbuild=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=SUSPENDED&bug_status=WAITING&bug_status=REOPENED&priority=P1&priority=P2&priority=P3&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0=">Serious ----------------------------------------------------------------------- Summary of changes: htdocs/index.html | 10 +++++++--- 1 file changed, 7 insertions(+), 3 deletions(-) hooks/post-receive -- gcc-wwwdocs
reply other threads:[~2022-04-21 9:09 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=20220421090927.6A8413856DD5@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: 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).