public inbox for gcc-cvs-wwwdocs@sourceware.org
help / color / mirror / Atom feed
From: Philipp Tomsich <ptomsich@sourceware.org>
To: gcc-cvs-wwwdocs@gcc.gnu.org
Subject: gcc-wwwdocs branch master updated. 6bffab91722c4f22d0e00c7197cf15e716dd7f63
Date: Mon, 14 Nov 2022 15:31:43 +0000 (GMT)	[thread overview]
Message-ID: <20221114153143.835B83858D1E@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  6bffab91722c4f22d0e00c7197cf15e716dd7f63 (commit)
      from  d851981b4b279e1ca77d22183e84600234cebc69 (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 6bffab91722c4f22d0e00c7197cf15e716dd7f63
Author: Philipp Tomsich <philipp.tomsich@vrull.eu>
Date:   Mon Nov 14 16:31:38 2022 +0100

    gcc-13: aarch64: Fix typo in 'cortex-x3'

diff --git a/htdocs/gcc-13/changes.html b/htdocs/gcc-13/changes.html
index e0910f96..41d07e57 100644
--- a/htdocs/gcc-13/changes.html
+++ b/htdocs/gcc-13/changes.html
@@ -218,7 +218,7 @@ a work-in-progress.</p>
       <li>Ampere-1A (<code>ampere1a</code>).</li>
       <li>Arm Cortex-A715 (<code>cortex-a715</code>).</li>
       <li>Arm Cortex-X1C (<code>cortex-x1c</code>).</li>
-      <li>Arm Cortex-X3 (<code>cortex-c3</code>).</li>
+      <li>Arm Cortex-X3 (<code>cortex-x3</code>).</li>
       <li>Arm Neoverse V2 (<code>neoverse-v2</code>).</li>
     </ul>
 </ul>

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

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


hooks/post-receive
-- 
gcc-wwwdocs

                 reply	other threads:[~2022-11-14 15:31 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=20221114153143.835B83858D1E@sourceware.org \
    --to=ptomsich@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).