public inbox for gcc-cvs-wwwdocs@sourceware.org help / color / mirror / Atom feed
From: Jakub Jelinek <jakub@sourceware.org> To: gcc-cvs-wwwdocs@gcc.gnu.org Subject: gcc-wwwdocs branch master updated. d00b9c2010ef4efb458e5f3fba9ecb96adc901a9 Date: Thu, 29 Jul 2021 15:24:09 +0000 (GMT) [thread overview] Message-ID: <20210729152409.3C4F839B5D26@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 d00b9c2010ef4efb458e5f3fba9ecb96adc901a9 (commit) from 863f00a738d9181946580cdca179dfaeeb882d2d (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 d00b9c2010ef4efb458e5f3fba9ecb96adc901a9 Author: Jakub Jelinek <jakub@redhat.com> Date: Thu Jul 29 17:23:48 2021 +0200 Mention TR10 release. diff --git a/htdocs/projects/gomp/index.html b/htdocs/projects/gomp/index.html index 90e73175..ff14b2b2 100644 --- a/htdocs/projects/gomp/index.html +++ b/htdocs/projects/gomp/index.html @@ -69,6 +69,10 @@ available.</p> <h2>Status</h2> <dl> +<dt><b>July 15, 2021</b></dt> +<dd><p><a href="https://www.openmp.org/wp-content/uploads/openmp-TR10.pdf">OpenMP +Technical Report 10: Version 5.2 Public Comment Draft</a> has been released.</p></dd> + <dt><b>November 13, 2020</b></dt> <dd><p><a href="https://www.openmp.org/wp-content/uploads/OpenMP-API-Specification-5-1.pdf">OpenMP Version 5.1</a> has been released.</p></dd> ----------------------------------------------------------------------- Summary of changes: htdocs/projects/gomp/index.html | 4 ++++ 1 file changed, 4 insertions(+) hooks/post-receive -- gcc-wwwdocs
reply other threads:[~2021-07-29 15:24 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=20210729152409.3C4F839B5D26@sourceware.org \ --to=jakub@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).