public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Kwok Cheung Yeung <kcy@codesourcery.com>
To: GCC Patches <gcc-patches@gcc.gnu.org>
Subject: [COMMIT] wwwdocs: Document devel/omp/gcc-11
Date: Thu, 13 May 2021 22:28:59 +0100	[thread overview]
Message-ID: <8aed1c9e-dfa2-4e55-5d7f-dbe2a19e7875@codesourcery.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 370 bytes --]

Hello

I have pushed the devel/omp/gcc-11 branch to the git repo as the development 
branch for new OpenMP, OpenACC and offloading functionality, based on the GCC 11 
branch.

I have committed this patch to update the git doc page to point to the new 
branch as the active OMP develepment branch, and have moved devel/omp/gcc-10 to 
the list of inactive branches.

Kwok

[-- Attachment #2: og11.patch --]
[-- Type: text/plain, Size: 2565 bytes --]

commit 8a006e10264a471a8f9ece2ce3720eff0910f77d
Author: Kwok Cheung Yeung <kcy@codesourcery.com>
Date:   Thu May 13 22:09:36 2021 +0100

    Document devel/omp/gcc-11 branch
    
    This also moves the old devel/omp/gcc-10 branch to the inactive branches
    section next to devel/omp/gcc-9.

diff --git a/htdocs/git.html b/htdocs/git.html
index 8edde126..2bbfc334 100644
--- a/htdocs/git.html
+++ b/htdocs/git.html
@@ -280,15 +280,15 @@ in Git.</p>
   Makarov <a href="mailto:vmakarov@redhat.com">vmakarov@redhat.com</a>.
   </dd>
 
-  <dt><a href="https://gcc.gnu.org/git/gitweb.cgi?p=gcc.git;a=shortlog;h=refs/heads/devel/omp/gcc-10">devel/omp/gcc-10</a></dt>
+  <dt><a href="https://gcc.gnu.org/git/gitweb.cgi?p=gcc.git;a=shortlog;h=refs/heads/devel/omp/gcc-11">devel/omp/gcc-11</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</a> support (OMP:
   offloading and multi processing).
-  The branch is based on releases/gcc-10.
-  Please send patch emails with a short-hand <code>[og10]</code> tag in the
+  The branch is based on releases/gcc-11.
+  Please send patch emails with a short-hand <code>[og11]</code> tag in the
   subject line, and use <code>ChangeLog.omp</code> files.</dd>
 
   <dt>unified-autovect</dt>
@@ -949,13 +949,14 @@ merged.</p>
   respectively.</dd>
 
   <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 was used for collaborative development of
+  <dt><a href="https://gcc.gnu.org/git/gitweb.cgi?p=gcc.git;a=shortlog;h=refs/heads/devel/omp/gcc-10">devel/omp/gcc-10</a></dt>
+  <dd>These branches were used 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 as the successor to openacc-gcc-9-branch after the move to
+  functionality as the successors to openacc-gcc-9-branch after the move to
   Git.
-  The branch was based on releases/gcc-9.
-  Development has now moved to the devel/omp/gcc-10 branch.</dd>
+  The branches were based on releases/gcc-9 and releases/gcc-10 respectively.
+  Development has now moved to the devel/omp/gcc-11 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

                 reply	other threads:[~2021-05-13 21:29 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=8aed1c9e-dfa2-4e55-5d7f-dbe2a19e7875@codesourcery.com \
    --to=kcy@codesourcery.com \
    --cc=gcc-patches@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).