From: NotYourFox <contact@notyourfox.coffee>
To: james.bottomley@hansenpartnership.com
Cc: geert@linux-m68k.org, gregkh@linuxfoundation.org,
linux-kernel@vger.kernel.org, patches@lists.linux.dev
Subject: Re: [PATCH] MAINTAINERS: Remove some entries due to various compliance requirements.
Date: Thu, 24 Oct 2024 21:41:25 +0300 [thread overview]
Message-ID: <51b4a9dc-42a8-4d3d-bd1d-2a5548bdc5b1@notyourfox.coffee> (raw)
In-Reply-To: <7ee74c1b5b589619a13c6318c9fbd0d6ac7c334a.camel@HansenPartnership.com>
Thanks for clarification.
It could be a "good enough" explanation to settle things down. If not
for Linus' reply.
One message made him lose most of the respect he earned in Russia for
good things. More importantly, our trust in Linux and FOSS in general.
Very, very disappointing, even more to me as I don't see any better
alternatives.
Linus is a developer, a hacker, and one of the names everyone thinks
about when it comes to FOSS. Not one of those arrogant politicians. He
should have never changed.
Signed,
forever a Linux user.
next prev parent reply other threads:[~2024-10-24 18:41 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <2024101835-tiptop-blip-09ed@gregkh>
2024-10-21 7:49 ` Geert Uytterhoeven
2024-10-21 16:29 ` Wolfram Sang
2024-10-24 6:56 ` Lukas Wunner
2024-10-24 15:39 ` James Bottomley
2024-10-24 18:41 ` NotYourFox [this message]
2024-10-25 11:43 ` 14071 | " Michael Shigorin
2024-10-25 23:44 ` Vladimir Smirnov
2024-10-26 12:00 ` Angry Dev
2024-10-26 16:27 ` John Mcenroy
2024-10-30 13:34 ` metux
2024-10-21 12:02 ` Geert Uytterhoeven
2024-10-24 15:56 ` [PATCH] MAINTAINERS: Remove some entries due to various moral requirements Enrico Weigelt, metux IT consult
2024-10-27 20:20 ` [PATCH] MAINTAINERS: Remove some entries due to various compliance requirements Alexander Pevzner
2024-10-25 21:12 Joe Putin
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=51b4a9dc-42a8-4d3d-bd1d-2a5548bdc5b1@notyourfox.coffee \
--to=contact@notyourfox.coffee \
--cc=geert@linux-m68k.org \
--cc=gregkh@linuxfoundation.org \
--cc=james.bottomley@hansenpartnership.com \
--cc=linux-kernel@vger.kernel.org \
--cc=patches@lists.linux.dev \
/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
all inboxes | Powered by JetHome®