public inbox for gcc-cvs-wwwdocs@sourceware.org help / color / mirror / Atom feed
From: tschwinge@gcc.gnu.org To: gcc-cvs-wwwdocs@gcc.gnu.org Subject: gcc-wwwdocs branch master updated. 6b92a4c7033db33ed5b6827e826a561077ed2181 Date: Tue, 03 Mar 2020 13:43:00 -0000 [thread overview] Message-ID: <20200303134359.81678.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 6b92a4c7033db33ed5b6827e826a561077ed2181 (commit) from 039a5698a0895d2b9af9f321b33ba293928b2fb9 (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 6b92a4c7033db33ed5b6827e826a561077ed2181 Author: Thomas Schwinge <thomas@schwinge.name> Date: Tue Mar 3 14:37:36 2020 +0100 Document devel/omp/gcc-9 branch ..., and retire openacc-gcc-9-branch. diff --git a/htdocs/git.html b/htdocs/git.html index 7fd22a9..bec93ea 100644 --- a/htdocs/git.html +++ b/htdocs/git.html @@ -280,19 +280,16 @@ in Git.</p> Makarov <a href="mailto:vmakarov@redhat.com">vmakarov@redhat.com</a>. </dd> - <dt><a href="https://gcc.gnu.org/wiki/OpenACC">openacc-gcc-9-branch</a></dt> - <dd>This <a href="https://gcc.gnu.org/wiki/GitMirror">Git-only branch</a> is - used for collaborative development - of <a href="https://gcc.gnu.org/wiki/OpenACC">OpenACC support</a> and related + <dt><a href="https://gcc.gnu.org/git/gitweb.cgi?p=gcc.git;a=shortlog;h=refs/heads/devel/omp/gcc-9">devel/omp/gcc-9</a></dt> + <dd>This branch is for collaborative development of + <a href="https://gcc.gnu.org/wiki/OpenACC">OpenACC</a> and + <a href="https://gcc.gnu.org/wiki/openmp">OpenMP</a> support and related functionality, such - as <a href="https://gcc.gnu.org/wiki/Offloading">offloading support</a>. The - branch is based on gcc-9-branch. Find it - at <code>git://gcc.gnu.org/git/gcc.git</code>, - <<a href="https://gcc.gnu.org/git/?p=gcc.git;a=shortlog;h=refs/heads/openacc-gcc-9-branch">https://gcc.gnu.org/git/?p=gcc.git;a=shortlog;h=refs/heads/openacc-gcc-9-branch</a>>, - or - <<a href="https://github.com/gcc-mirror/gcc/tree/openacc-gcc-9-branch">https://github.com/gcc-mirror/gcc/tree/openacc-gcc-9-branch</a>>. + as <a href="https://gcc.gnu.org/wiki/Offloading">offloading</a> support (OMP: + offloading and multi processing). + The branch is based on releases/gcc-9. Please send patch emails with a short-hand <code>[og9]</code> tag in the - subject line, and use <code>ChangeLog.openacc</code> files.</dd> + subject line, and use <code>ChangeLog.omp</code> files.</dd> <dt>unified-autovect</dt> <dd>This branch is for work on improving effectiveness and generality of GCC's @@ -943,10 +940,12 @@ merged.</p> <dt>openacc-gcc-7-branch</dt> <dt>openacc-gcc-8-branch</dt> + <dt>openacc-gcc-9-branch</dt> <dd>These branches were used for development of <a href="https://gcc.gnu.org/wiki/OpenACC">OpenACC support</a> and related - functionality, based on gcc-7-branch and gcc-8-branch respectively. - Work is now proceeding on the openacc-gcc-9-branch.</dd> + functionality, based on gcc-7-branch, gcc-8-branch, and gcc-9-branch + respectively. + Work is now proceeding on the devel/omp/gcc-9 branch.</dd> <dt>hammer-3_3-branch</dt> <dd>The goal of this branch was to have a stable compiler based on GCC 3.3 ----------------------------------------------------------------------- Summary of changes: htdocs/git.html | 25 ++++++++++++------------- 1 file changed, 12 insertions(+), 13 deletions(-) hooks/post-receive -- gcc-wwwdocs
reply other threads:[~2020-03-03 13:43 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=20200303134359.81678.qmail@sourceware.org \ --to=tschwinge@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).