All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Enrico Weigelt, metux IT consult" <lkml@metux.net>
To: Kexy Biscuit <kexybiscuit@aosc.io>,
	jeffbai@aosc.io, gregkh@linuxfoundation.org,
	wangyuli@uniontech.com, torvalds@linux-foundation.org
Cc: aospan@netup.ru, conor.dooley@microchip.com,
	ddrokosov@sberdevices.ru, dmaengine@vger.kernel.org,
	dushistov@mail.ru, fancer.lancer@gmail.com, geert@linux-m68k.org,
	hoan@os.amperecomputing.com, ink@jurassic.park.msu.ru,
	linux-alpha@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org, linux-fpga@vger.kernel.org,
	linux-gpio@vger.kernel.org, linux-hwmon@vger.kernel.org,
	linux-ide@vger.kernel.org, linux-iio@vger.kernel.org,
	linux-media@vger.kernel.org, linux-mips@vger.kernel.org,
	linux-renesas-soc@vger.kernel.org, linux-spi@vger.kernel.org,
	manivannan.sadhasivam@linaro.org, mattst88@gmail.com,
	netdev@vger.kernel.org, nikita@trvn.ru, ntb@lists.linux.dev,
	patches@lists.linux.dev, richard.henderson@linaro.org,
	s.shtylyov@omp.ru, serjk@netup.ru, shc_work@mail.ru,
	tsbogend@alpha.franken.de, v.georgiev@metrotek.ru,
	wsa+renesas@sang-engineering.com, xeb@mail.ru
Subject: Re: [PATCH] Revert "MAINTAINERS: Remove some entries due to various compliance requirements."
Date: Thu, 24 Oct 2024 17:05:13 +0200	[thread overview]
Message-ID: <64ef261c-82d0-4fad-ba8a-562f247340fb@metux.net> (raw)
In-Reply-To: <20241023080935.2945-2-kexybiscuit@aosc.io>

On 23.10.24 10:09, Kexy Biscuit wrote:
> This reverts commit 6e90b675cf942e50c70e8394dfb5862975c3b3b2.
>
> An absolutely no-one-ever-reviewed patch, not even by the maintainers who
> got removed themselves - at least not on the mailing list. Then the patch
> just got slipped into an unrelated subsystem pull request, and got pulled
> by Torvalds with not even a comment.
>
> What about the next time? Who next would be removed from the MAINTAINERS
> file, the kernel.org infrastructure? What if the compliance requires
> another XZ backdoor to be developed without further explanation? Is the
> kernel development process still done in public?
>
> Are the "compliance requirements" documented on docs.kernel.org? Who are
> responsible for them? Are all that are responsible employees of
> The Linux Foundation, which is regulated by the U.S. legislature?

<snip>

Reviewed-By: Enrico Weigelt <info@metux.net>


And, no, don't anybody dare calling me a "Russian troll" !

I grew up in the GDR, which was factually Russian/Soviet-occupied for 40
years. I grew up behind the iron curtain. And part of my family coming
from near Mariuopol. They also suffered from that horrible war (and many
of the wider family fled to Germany).

The only way for stopping that suffering is arranging peace. The longer
the war goes on, the more suffering, the more people just DIE.

Expelling people just because they happen to live in Russia (or maybe
just having an .ru mail address) isn't doing anything for peace - it's
the opposite: it's widening the war. It's rebuiling the iron curtain,
this time into one of the most international projects of mankind.
And it's just rascist.

If we really want to expell people for living in countries that are
starting wars or committing war crimes, then have a closer look at
who's leading the bodycount "highscore" since WW2. Spoiler: it's not
Russia - it's the anglo-american block. And guess who's leading the
hall of shame of using weapons of mass destruction: the US (and their
vassals).

Who's the only nation who used nuclear bombs against civilians ?
The US. And who's still using DU munition (also a WoMD - contanimates
the soil for at least centuries) ? The NATO (yes, including Germany)

Does anybody see where this all is going ?


Wars cannot be ended by more war. Only by peace.


--mtx

--
---
Hinweis: unverschlüsselte E-Mails können leicht abgehört und manipuliert
werden ! Für eine vertrauliche Kommunikation senden Sie bitte ihren
GPG/PGP-Schlüssel zu.
---
Enrico Weigelt, metux IT consult
Free software and Linux embedded engineering
info@metux.net -- +49-151-27565287


  parent reply	other threads:[~2024-10-24 15:07 UTC|newest]

Thread overview: 61+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-18 11:31 [PATCH] MAINTAINERS: Remove some entries due to various compliance requirements Greg Kroah-Hartman
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
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-23  6:30 ` WangYuli
2024-10-23  7:32   ` Mingcong Bai
2024-10-23  8:09     ` [PATCH] Revert "MAINTAINERS: Remove some entries due to various compliance requirements." Kexy Biscuit
2024-10-23  8:26       ` Nikita Travkin
2024-10-23  8:35         ` WangYuli
2024-10-23  9:04       ` Mingcong Bai
2024-10-23  9:28       ` Tonghao Zhang
2024-10-23 10:27       ` Nikita Shubin
2024-10-23 14:47       ` Lance Yang
2024-10-23 15:03       ` Yangyu Chen
2024-10-23 15:04       ` Sergio Paracuellos
2024-10-23 16:22       ` Yao Zi
2024-10-23 16:51       ` Tor Vic
2024-10-23 17:45         ` Linus Torvalds
2024-10-23 18:56           ` Phillip Susi
2024-10-23 19:15           ` Peter Cai
2024-10-23 19:19             ` Linus Torvalds
2024-10-23 19:28               ` Peter Cai
2024-10-24 21:01               ` Mikhail Novosyolov
2024-10-25  7:11                 ` Nikolay Kichukov
2024-10-23 19:50           ` Tor Vic
2024-10-23 22:14           ` NotYourFox
2024-10-24  7:11           ` Integral
2024-10-24  8:02           ` crupest
2024-10-24  9:53           ` what about CoC? (was: [PATCH] Revert "MAINTAINERS: Remove some entries due to various compliance requirements.") Michael Shigorin
2025-10-01 10:11             ` Michael Shigorin
2025-10-03 15:48               ` what about CoC? Alexander Lobakin
2025-10-03 16:45                 ` Michael Shigorin
2024-10-24  9:57           ` [PATCH] Revert "MAINTAINERS: Remove some entries due to various compliance requirements." Ivan Epifanov
2024-10-24 15:41             ` Andy Shevchenko
2024-10-24 16:15               ` Guenter Roeck
2024-10-24 17:13                 ` Ivan Epifanov
2024-10-24 17:18                   ` Guenter Roeck
2024-10-24 17:38                     ` Ivan Epifanov
2024-10-24 17:28                 ` Nopempele N
2024-10-24 17:07               ` Ivan Epifanov
2024-10-24 17:45                 ` Sergey Shtylyov
2024-10-25 18:39           ` Tor Vic
     [not found]           ` <20241024140353.384881-1-vladimir_putin_rus@kremlin.ru>
     [not found]             ` <20241024140353.384881-2-vladimir_putin_rus@kremlin.ru>
2024-10-30 12:48               ` lore.kernel.org getting senile ? [WAS: [PATCH 1/2] MAINTAINERS: Remove Huawei due to compilance requirements metux
2024-10-24 15:05       ` Enrico Weigelt, metux IT consult [this message]
2024-10-24 15:33         ` [PATCH] Revert "MAINTAINERS: Remove some entries due to various compliance requirements." Andy Shevchenko
2024-10-23  8:26     ` [PATCH] MAINTAINERS: Remove some entries due to various compliance requirements Mingcong Bai
2024-10-23  9:38       ` WangYuli
2024-10-23  9:53       ` Jiaxun Yang
2024-10-23 10:10         ` Mingcong Bai
2024-10-23  8:37 ` Mauro Carvalho Chehab
2024-10-23 10:22 ` Nikita Shubin
2024-10-24 15:56 ` [PATCH] MAINTAINERS: Remove some entries due to various moral requirements Enrico Weigelt, metux IT consult
2024-10-26  6:37 ` [PATCH] MAINTAINERS: Remove some entries due to various compliance requirements SekiBetu
2024-10-27 20:20 ` Alexander Pevzner
  -- strict thread matches above, loose matches on Subject: below --
2024-10-25  8:46 [PATCH] Revert "MAINTAINERS: Remove some entries due to various compliance requirements." thomas superb

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=64ef261c-82d0-4fad-ba8a-562f247340fb@metux.net \
    --to=lkml@metux.net \
    --cc=aospan@netup.ru \
    --cc=conor.dooley@microchip.com \
    --cc=ddrokosov@sberdevices.ru \
    --cc=dmaengine@vger.kernel.org \
    --cc=dushistov@mail.ru \
    --cc=fancer.lancer@gmail.com \
    --cc=geert@linux-m68k.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=hoan@os.amperecomputing.com \
    --cc=ink@jurassic.park.msu.ru \
    --cc=jeffbai@aosc.io \
    --cc=kexybiscuit@aosc.io \
    --cc=linux-alpha@vger.kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-fpga@vger.kernel.org \
    --cc=linux-gpio@vger.kernel.org \
    --cc=linux-hwmon@vger.kernel.org \
    --cc=linux-ide@vger.kernel.org \
    --cc=linux-iio@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=linux-mips@vger.kernel.org \
    --cc=linux-renesas-soc@vger.kernel.org \
    --cc=linux-spi@vger.kernel.org \
    --cc=manivannan.sadhasivam@linaro.org \
    --cc=mattst88@gmail.com \
    --cc=netdev@vger.kernel.org \
    --cc=nikita@trvn.ru \
    --cc=ntb@lists.linux.dev \
    --cc=patches@lists.linux.dev \
    --cc=richard.henderson@linaro.org \
    --cc=s.shtylyov@omp.ru \
    --cc=serjk@netup.ru \
    --cc=shc_work@mail.ru \
    --cc=torvalds@linux-foundation.org \
    --cc=tsbogend@alpha.franken.de \
    --cc=v.georgiev@metrotek.ru \
    --cc=wangyuli@uniontech.com \
    --cc=wsa+renesas@sang-engineering.com \
    --cc=xeb@mail.ru \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.