public inbox for gcc-cvs-wwwdocs@sourceware.org help / color / mirror / Atom feed
From: Tobias Burnus <burnus@sourceware.org> To: gcc-cvs-wwwdocs@gcc.gnu.org Subject: gcc-wwwdocs branch master updated. d2aa37c82988a64079ff90654eba16d4d19695b7 Date: Tue, 23 May 2023 06:46:24 +0000 (GMT) [thread overview] Message-ID: <20230523064624.9FDDA385840E@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 d2aa37c82988a64079ff90654eba16d4d19695b7 (commit) from 4013044e02d0b04430531bb604ddb201c51cb238 (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 d2aa37c82988a64079ff90654eba16d4d19695b7 Author: Tobias Burnus <tobias@codesourcery.com> Date: Tue May 23 08:45:17 2023 +0200 projects/gomp: Link to GCC 13 impl. status as well diff --git a/htdocs/projects/gomp/index.html b/htdocs/projects/gomp/index.html index fa770855..cb2338f3 100644 --- a/htdocs/projects/gomp/index.html +++ b/htdocs/projects/gomp/index.html @@ -143,6 +143,8 @@ filing a <a href="../../bugs/">bug report</a>.</p> <p>Implementation status in libgomp manual: <a href="https://gcc.gnu.org/onlinedocs/libgomp/OpenMP-Implementation-Status.html" >Mainline (GCC 13)</a>, +<a href="https://gcc.gnu.org/onlinedocs/gcc-13.1.0/libgomp/OpenMP-Implementation-Status.html" +>GCC 13</a>.</p> <a href="https://gcc.gnu.org/onlinedocs/gcc-12.1.0/libgomp/OpenMP-Implementation-Status.html" >GCC 12</a>.</p> ----------------------------------------------------------------------- Summary of changes: htdocs/projects/gomp/index.html | 2 ++ 1 file changed, 2 insertions(+) hooks/post-receive -- gcc-wwwdocs
reply other threads:[~2023-05-23 6:46 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=20230523064624.9FDDA385840E@sourceware.org \ --to=burnus@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).