public inbox for gcc-cvs-wwwdocs@sourceware.org
help / color / mirror / Atom feed
From: Kwok Yeung <kcy@sourceware.org>
To: gcc-cvs-wwwdocs@gcc.gnu.org
Subject: gcc-wwwdocs branch master updated. 0695e5e969eba730e517a6adbdf38b8774f89437
Date: Wed, 29 Jun 2022 21:38:04 +0000 (GMT)	[thread overview]
Message-ID: <20220629213804.8E06C384D142@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  0695e5e969eba730e517a6adbdf38b8774f89437 (commit)
      from  85db6afe1540962730dbee1aea6064b015e60ee0 (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 0695e5e969eba730e517a6adbdf38b8774f89437
Author: Kwok Cheung Yeung <kcy@codesourcery.com>
Date:   Wed Jun 29 22:32:39 2022 +0100

    Document devel/omp/gcc-12 branch
    
    Also moves the old devel/omp/gcc-11 branch to the inactive branches
    section next to devel/omp/gcc-10.

diff --git a/htdocs/git.html b/htdocs/git.html
index 5202363c..52ad05db 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-11">devel/omp/gcc-11</a></dt>
+  <dt><a href="https://gcc.gnu.org/git/gitweb.cgi?p=gcc.git;a=shortlog;h=refs/heads/devel/omp/gcc-12">devel/omp/gcc-12</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-11.
-  Please send patch emails with a short-hand <code>[og11]</code> tag in the
+  The branch is based on releases/gcc-12.
+  Please send patch emails with a short-hand <code>[og12]</code> tag in the
   subject line, and use <code>ChangeLog.omp</code> files.</dd>
 
   <dt>unified-autovect</dt>
@@ -895,13 +895,15 @@ merged.</p>
 
   <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>
   <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>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 successors to openacc-gcc-9-branch after the move to
   Git.
-  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>
+  The branches were based on releases/gcc-9, releases/gcc-10 and
+  releases/gcc-11 respectively.
+  Development has now moved to the devel/omp/gcc-12 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 | 12 +++++++-----
 1 file changed, 7 insertions(+), 5 deletions(-)


hooks/post-receive
-- 
gcc-wwwdocs


                 reply	other threads:[~2022-06-29 21:38 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=20220629213804.8E06C384D142@sourceware.org \
    --to=kcy@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: 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).