From: Giacomo Tesio <giacomo@tesio.it>
To: Richard Biener <richard.guenther@gmail.com>
Cc: Gabriel Ravier <gabravier@gmail.com>,
Valentino Giudice <valentino.giudice96@gmail.com>,
"gcc@gcc.gnu.org" <gcc@gcc.gnu.org>
Subject: Re: GCC Mission Statement
Date: Wed, 09 Jun 2021 15:26:03 +0000 [thread overview]
Message-ID: <5F9B35A9-CAD4-44A3-8132-0DCA2ADDC601@tesio.it> (raw)
In-Reply-To: <CAFiYyc1N3MVAUwC37PmxqY708jHdxSdZpRaLkAkTN5TWAbJF=w@mail.gmail.com>
Sure Richard, I know.
On June 9, 2021 2:32:22 PM UTC, Richard Biener wrote:
>
> You are free to create "DCO-free" branches for the GCC 11 series
> (and older), reverting any DCO "incumbered" backports that reach
> the official GCC branches for those series.
I could.
Like all other people affected by the change.
If they know they should.
But isn't this a responsibility inversion?
I wonder: is this how you treat your users?
"Go fuck yourself" but politely stated?
To be honest, this comes to me as a great surprise.
That's what one would expect by the random guy on github, not by employees
of RedHat or Google serving as the Steering Committee of GCC.
Giacomo
next prev parent reply other threads:[~2021-06-09 15:26 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-09 4:43 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 [this message]
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
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=5F9B35A9-CAD4-44A3-8132-0DCA2ADDC601@tesio.it \
--to=giacomo@tesio.it \
--cc=gabravier@gmail.com \
--cc=gcc@gcc.gnu.org \
--cc=richard.guenther@gmail.com \
--cc=valentino.giudice96@gmail.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).