public inbox for gcc-cvs-wwwdocs@sourceware.org help / color / mirror / Atom feed
From: Gerald Pfeifer <gerald@sourceware.org> To: gcc-cvs-wwwdocs@gcc.gnu.org Subject: gcc-wwwdocs branch master updated. 1b32b72e399b97aa54cb0b72e06d2e56420cce3f Date: Sun, 27 Dec 2020 18:48:08 +0000 (GMT) [thread overview] Message-ID: <20201227184808.6717A3846079@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 1b32b72e399b97aa54cb0b72e06d2e56420cce3f (commit) from 3cf814a3f9dc96d00b28e0c8b7db5c62805d5b7f (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 1b32b72e399b97aa54cb0b72e06d2e56420cce3f Author: Gerald Pfeifer <gerald@pfeifer.com> Date: Sun Dec 27 19:37:36 2020 +0100 git: Move cilkplus to Inactive branches Cilk Plus has been deprecated more than two years ago and not seen development on the GCC side for a while, too. The certificate for www.cilkplus.org expired four weeks ago, so remove our link there as we move the Cilk Plus entry to the section of Inactive Development branches. diff --git a/htdocs/git.html b/htdocs/git.html index 305d0c93..41bbe35b 100644 --- a/htdocs/git.html +++ b/htdocs/git.html @@ -442,14 +442,6 @@ in Git.</p> <dd>This branch is for development of a C++ modules system. It is maintained by <a href="mailto:nathan@acm.org">Nathan Sidwell</a>.</dd> - <dt>cilkplus</dt> - <dd>This branch is for the development of - <a href="https://www.cilkplus.org">Cilk Plus</a> language extension support - on GCC and G++ compilers. This branch is maintained by - <a href="mailto:balaji.v.iyer@intel.com">Balaji V. Iyer</a>. - Patches to this branch must be prefixed with <code>[cilkplus]</code> in the - subject line. It is also highly encouraged to CC the maintainer.</dd> - <dt>fortran-dev</dt> <dd>This branch is for disruptive changes to the Fortran front end, especially for OOP development and @@ -822,6 +814,13 @@ merged.</p> the code size optimization of GCC with code factoring methods (code motion and merging algorithms). It is no longer maintained.</dd> + <dt>cilkplus</dt> + <dd>This branch is for the development of Cilk Plus language extension + support on GCC and G++ compilers. This branch is maintained by + <a href="mailto:balaji.v.iyer@intel.com">Balaji V. Iyer</a>. + Patches to this branch must be prefixed with <code>[cilkplus]</code> in + the subject. It is also highly encouraged to CC the maintainer.</dd> + <dt>compile-server-branch</dt> <dd>This branch was aimed at improving compile speed by caching work done between compilations. The work saved is mainly related to header ----------------------------------------------------------------------- Summary of changes: htdocs/git.html | 15 +++++++-------- 1 file changed, 7 insertions(+), 8 deletions(-) hooks/post-receive -- gcc-wwwdocs
reply other threads:[~2020-12-27 18:48 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=20201227184808.6717A3846079@sourceware.org \ --to=gerald@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).