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. dc61fd633178bb66ebb0cba5783cd81ada84b813 Date: Wed, 31 Mar 2021 19:03:14 +0000 (GMT) [thread overview] Message-ID: <20210331190314.8BC80384C003@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 dc61fd633178bb66ebb0cba5783cd81ada84b813 (commit) from 7a3bc40387dde4fd827c8a6d233757f1f6137d59 (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 dc61fd633178bb66ebb0cba5783cd81ada84b813 Author: Gerald Pfeifer <gerald@pfeifer.com> Date: Wed Mar 31 19:11:03 2021 +0200 Don't list RMS as member of the Steering Committee Per https://gcc.gnu.org/pipermail/gcc/2021-March/235245.html "In 2012 RMS was added to the GCC Steering Committee web page based on his role in the GNU Project, though his role as a member of the Steering Committee has been ambiguous and he was not a member of the Steering Committee when EGCS became GCC[1]. We no longer feel that this listing serves the best interests of the GCC developer and user community. Therefore, we are removing him from the page. GCC supports the principles of Free Software and has remained aligned with the GNU Project since EGCS became GCC, but effectively has continued to operate as an autonomous project. The GCC Steering Committee is committed to providing a friendly, safe and welcoming environment for all, regardless of gender identity and expression, sexual orientation, disabilities, neurodiversity, physical appearance, body size, ethnicity, nationality, race, age, religion, or similar personal characteristics. - The GCC Steering Committee [1] https://static.lwn.net/1999/0429/a/gcc.html" diff --git a/htdocs/steering.html b/htdocs/steering.html index 53faba78..7192b424 100644 --- a/htdocs/steering.html +++ b/htdocs/steering.html @@ -44,12 +44,6 @@ place to reach them is the gcc <a href="lists.html">mailing list</a>.</p> <li>Jim Wilson (SiFive)</li> </ul> -<p>and</p> - -<ul> -<li>Richard Stallman (Free Software Foundation)</li> -</ul> - <p>Membership in the steering committee is a personal membership. Affiliations are listed for identification purposes only; steering committee members do not represent their employers or academic ----------------------------------------------------------------------- Summary of changes: htdocs/steering.html | 6 ------ 1 file changed, 6 deletions(-) hooks/post-receive -- gcc-wwwdocs
reply other threads:[~2021-03-31 19:03 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=20210331190314.8BC80384C003@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).