public inbox for
help / color / mirror / Atom feed
From: Jakub Jelinek <>
Subject: gcc-wwwdocs branch master updated. 60490c6e19f9d854721f271964c0379254aac244
Date: Fri,  9 Sep 2022 18:32:21 +0000 (GMT)	[thread overview]
Message-ID: <> (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  60490c6e19f9d854721f271964c0379254aac244 (commit)
      from  371bca4c80f7eb47fd62e2f7b31294f4ad596a0c (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 60490c6e19f9d854721f271964c0379254aac244
Author: Jakub Jelinek <>
Date:   Fri Sep 9 20:32:13 2022 +0200

    Small tweak for last change.

diff --git a/htdocs/projects/cxx-status.html b/htdocs/projects/cxx-status.html
index 541a4256..1766d10b 100644
--- a/htdocs/projects/cxx-status.html
+++ b/htdocs/projects/cxx-status.html
@@ -649,8 +649,9 @@
       <td> Atomic Compare-and-Exchange with Padding Bits </td>
       <td><a href="">P0528R3</a></td>
       <td class="supported">
-        <a href="../gcc-11/changes.html#cxx">11</a> (compiler side only) </td>
-        <a href="../gcc-13/changes.html#cxx">13</a> (full) </td>
+        <a href="../gcc-11/changes.html#cxx">11</a> (compiler side only) <br/>
+        <a href="../gcc-13/changes.html#cxx">13</a> (full)
+      </td>
       <td> </td>


Summary of changes:
 htdocs/projects/cxx-status.html | 5 +++--
 1 file changed, 3 insertions(+), 2 deletions(-)


                 reply	other threads:[~2022-09-09 18:32 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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \

* 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).