public inbox for gcc-cvs-wwwdocs@sourceware.org help / color / mirror / Atom feed
From: gerald@gcc.gnu.org To: gcc-cvs-wwwdocs@gcc.gnu.org Subject: gcc-wwwdocs branch master updated. 1cda7199f758776f7a19638af8e0a9d3edfef193 Date: Thu, 23 Jan 2020 20:53:00 -0000 [thread overview] Message-ID: <20200123205310.64678.qmail@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 1cda7199f758776f7a19638af8e0a9d3edfef193 (commit) from 892edc602bd9f1d74151d854577fbeebc3546ff7 (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 1cda7199f758776f7a19638af8e0a9d3edfef193 Author: Gerald Pfeifer <gerald@pfeifer.com> Date: Thu Jan 23 16:27:42 2020 +0100 Abstract away verbal references to SVN in the GOMP project description. diff --git a/htdocs/projects/gomp/index.html b/htdocs/projects/gomp/index.html index 39c8d3ad..70e6d95a 100644 --- a/htdocs/projects/gomp/index.html +++ b/htdocs/projects/gomp/index.html @@ -69,7 +69,7 @@ href="https://www.openmp.org/wp-content/uploads/openmp-4.5.pdf">OpenMP v4.5</a> specification has been released.</p></dd> <dt><b>October 13, 2015</b></dt> -<dd><p>The <code>gomp-4_1-branch</code> has been merged into SVN +<dd><p>The <code>gomp-4_1-branch</code> has been merged into mainline, so GCC 6 and later will feature OpenMP v4.5 support for C and C++.</p></dd> @@ -80,10 +80,10 @@ GCC 4.9.1 release.</p></dd> <dt><b>June 18, 2014</b></dt> <dd><p>The last major part of Fortran OpenMP v4.0 support has been -committed into SVN mainline.</p></dd> +committed into mainline.</p></dd> <dt><b>October 11, 2013</b></dt> -<dd><p>The <code>gomp-4_0-branch</code> has been merged into SVN +<dd><p>The <code>gomp-4_0-branch</code> has been merged into mainline, so GCC 4.9 and later will feature OpenMP v4.0 support for C and C++.</p></dd> @@ -91,7 +91,7 @@ C and C++.</p></dd> <dd><p>The final OpenMP v4.0 specification has been released.</p></dd> <dt><b>August 2, 2011</b></dt> -<dd><p>The <code>gomp-3_1-branch</code> has been merged into SVN +<dd><p>The <code>gomp-3_1-branch</code> has been merged into mainline, so GCC 4.7 and later will feature OpenMP v3.1 support.</p></dd> <dt><b>July 9, 2011</b></dt> @@ -100,10 +100,10 @@ mainline, so GCC 4.7 and later will feature OpenMP v3.1 support.</p></dd> <dt><b>February 6, 2011</b></dt> <dd><p>A draft of the OpenMP v3.1 specification has been released for public review. The <code>gomp-3_1-branch</code> branch has been -created in SVN and work began on implementing v3.1 support.</p></dd> +created and work began on implementing v3.1 support.</p></dd> <dt><b>June 6, 2008</b></dt> -<dd><p>The <code>gomp-3_0-branch</code> has been merged into SVN +<dd><p>The <code>gomp-3_0-branch</code> has been merged into mainline, so GCC 4.4 and later will feature OpenMP v3.0 support.</p></dd> <dt><b>May 12, 2008</b></dt> @@ -112,7 +112,7 @@ mainline, so GCC 4.4 and later will feature OpenMP v3.0 support.</p></dd> <dt><b>October 22, 2007</b></dt> <dd><p>Draft of the OpenMP v3.0 specification has been released for public review, the <code>gomp-3_0-branch</code> branch has been -created in SVN and work began on implementing v3.0 support.</p></dd> +created and work began on implementing v3.0 support.</p></dd> <dt><b>March 9, 2006</b></dt> <dd><p>The branch has been merged into mainline, so starting with ----------------------------------------------------------------------- Summary of changes: htdocs/projects/gomp/index.html | 14 +++++++------- 1 file changed, 7 insertions(+), 7 deletions(-) hooks/post-receive -- gcc-wwwdocs
reply other threads:[~2020-01-23 20:53 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=20200123205310.64678.qmail@sourceware.org \ --to=gerald@gcc.gnu.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).