public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Aaron Gyes <aaronite@icloud.com>
To: GCC Administrator via Gcc <gcc@gcc.gnu.org>
Subject: Re: Mission Statement
Date: Wed, 9 Jun 2021 08:49:43 -0700	[thread overview]
Message-ID: <ECDB1A59-9317-48EC-BC02-3F03607F9D1E@icloud.com> (raw)
In-Reply-To: <trinity-d5e4b50f-600c-41dd-a628-e2c1d0103604-1623252603196@3c-app-mailcom-bs05>

On Jun 9, 2021, at 8:30 AM, Christopher Dimech <dimech@gmx.com> wrote:
> 
> Besides inspiring a sceptic attitude, Cicero made the language of
> the civilized world.

Yes

> This has nothing to do with any complaints
> of mistreatment, but mostly about belief systems that have taken
> over many people's lives.  That's what is most embarrassing.

Huh

> 
> After all, it was yourself who criticised my attitude towards Liu
> Hao, who had stated on 4/10/2021 the greatness of chairman mao
> and how he eradicated discrimination from chinese society.  Once
> you take on such zeal, you will get so badly identified with it,
> that you yourself will became a social problem.
> 
> The chinese communist party killed thousands of people every year
> by firing squads, lethal injection and mobile death vans.  Not to
> mention the horrifying child-killing policy during china's
> draconian one-child system.  It has recently also became infamous
> for forced uighur sterilisation.  How can I ever agree with
> someone who thinks the suppression of others is good!

Are you asserting I was wrong in my observations that day? Do you
think I disagree with anything in the second quoted paragraph?
Would it matter? Oh, why do I let myself get sucked in?

What even is that kind of argument occurring post “After all,”?

I can’t figure out if this is just a non-sequitur, and/or a straw
man, or part of a gish gallop? Something just pathological?
Perhaps I should go get checked and make sure I didn’t have a stroke
since it seems like I must be having trouble processing my
environment: it seems like you’ve been behaving this way on the
mailing list for months and apparently nobody in charge has asked
you to do better or stop and everyone here is pretty smart and
professional.

Aaron

  parent reply	other threads:[~2021-06-09 15:49 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-09  4:43 GCC " Valentino Giudice
2021-06-09  4:56 ` Siddhesh Poyarekar
2021-06-09  5:09   ` Valentino Giudice
2021-06-09  5:32     ` Siddhesh Poyarekar
2021-06-11  4:42       ` Valentino Giudice
2021-06-09  6:31     ` Didier Kryn
2021-06-09  9:44     ` Gabriel Ravier
2021-06-09 10:11       ` Giacomo Tesio
2021-06-09 12:41         ` Gabriel Ravier
2021-06-09 14:22           ` Giacomo Tesio
2021-06-09 14:32             ` Richard Biener
2021-06-09 15:26               ` Giacomo Tesio
2021-06-09 15:34                 ` Christopher Dimech
2021-06-09 13:48   ` Christopher Dimech
2021-06-09 14:02     ` Aaron Gyes
     [not found]     ` <01624AC3-781E-4AAC-A469-87A777AD50DA@icloud.com>
     [not found]       ` <trinity-d5e4b50f-600c-41dd-a628-e2c1d0103604-1623252603196@3c-app-mailcom-bs05>
2021-06-09 15:49         ` Aaron Gyes [this message]
2021-06-09 20:49           ` Christopher Dimech
2021-06-09 21:07             ` Aaron Gyes
2021-06-10  3:10               ` Christopher Dimech
2021-06-11  4:58 ` GCC " Valentino Giudice

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=ECDB1A59-9317-48EC-BC02-3F03607F9D1E@icloud.com \
    --to=aaronite@icloud.com \
    --cc=gcc@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).