From: Giacomo Tesio <giacomo@tesio.it>
To: Jonathan Wakely <jwakely.gcc@gmail.com>
Cc: Thomas Rodgers <rodgert@appliantology.com>,
Nathan Sidwell <nathan@acm.org>,
JeanHeyd Meneide <phdofthehouse@gmail.com>,
"gcc@gcc.gnu.org" <gcc@gcc.gnu.org>
Subject: Re: RMS removed from the GCC Steering Committee
Date: Fri, 2 Apr 2021 16:06:45 +0200 [thread overview]
Message-ID: <20210402160645.000029d6@tesio.it> (raw)
In-Reply-To: <CAH6eHdTqWU+XqOkAe7EvX2ufKVPjNTb+fJq48ffSL3g3i69SYQ@mail.gmail.com>
Dear Jonathan,
everybody can see it...
On Fri, 2 Apr 2021 14:05:10 +0100 Jonathan Wakely wrote:
> On Fri, 2 Apr 2021 at 11:06, Giacomo Tesio wrote:
> > But from outside your "cultural bubble", we all see that a bunch of
> > highly controversial [3][4] US corporations (with long term ties
> > with the USA DoD [5]) are kicking out of the GCC Steering Committee
> > their only connection with both the FSF and the GNU project.
>
> If that's what you think happened, you've not been paying attention to
> this thread.
...I wrote such a long mail, full of references to so many passages of
your mails in these threads... without paying attention to them.
What a lucky guy, I am! :-D
> The SC just did was they were requested to do by (some
> of) the developers of the project.
Yeah, "some of".
In this specific moment, when a global (and well financed) mob is
attacking RMS personally, for anything they can frame as mischief,
you were fine to comply with what "some of the developers" asked.
What about the others?
Did you consider that many of them might be to scared to oppose?
Yet my request is not about Stallman, but about the Steering Committee.
Please fix the huge global hazard that his removal uncovered.
Giacomo
next prev parent reply other threads:[~2021-04-02 14:07 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-31 23:11 RMS removed from the GCC Steering Committee (was: Remove RMS...) Giacomo Tesio
2021-03-31 23:35 ` Jeff Law
2021-04-01 0:04 ` Giacomo Tesio
2021-04-01 1:25 ` RMS removed from the GCC Steering Committee Thomas Rodgers
2021-04-02 10:05 ` Giacomo Tesio
2021-04-02 11:50 ` Christopher Dimech
2021-04-02 13:05 ` Jonathan Wakely
2021-04-02 14:06 ` Giacomo Tesio [this message]
2021-04-02 14:39 ` Christopher Dimech
2021-04-02 21:25 ` Ian Lance Taylor
2021-04-03 17:31 ` Giacomo Tesio
2021-04-03 19:33 ` Jonathan Wakely
2021-04-03 23:45 ` Ian Lance Taylor
2021-04-04 9:22 ` Jonathan Wakely
2021-04-04 13:10 ` Giacomo Tesio
2021-04-04 13:49 ` Richard Kenner
2021-04-04 14:38 ` Giacomo Tesio
2021-04-04 17:59 ` Richard Kenner
2021-04-04 14:40 ` Christopher Dimech
2021-04-04 22:53 ` Ian Lance Taylor
2021-04-04 1:08 ` David Edelsohn
2021-04-01 9:13 ` RMS removed from the GCC Steering Committee (was: Remove RMS...) Jonathan Wakely
2021-04-01 9:23 ` Jonathan Wakely
2021-04-03 0:22 ` Gerald Pfeifer
2021-04-01 8:06 ` RMS removed from the GCC Steering Committee Andrea Corallo
2021-04-04 14:57 Christopher Dimech
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=20210402160645.000029d6@tesio.it \
--to=giacomo@tesio.it \
--cc=gcc@gcc.gnu.org \
--cc=jwakely.gcc@gmail.com \
--cc=nathan@acm.org \
--cc=phdofthehouse@gmail.com \
--cc=rodgert@appliantology.com \
/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).