From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: patches@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] MAINTAINERS: Remove some entries due to various compliance requirements.
Date: Mon, 21 Oct 2024 09:49:56 +0200 (CEST) [thread overview]
Message-ID: <a520d1f5-8273-d67e-97fe-67f73edce9f1@linux-m68k.org> (raw)
In-Reply-To: <2024101835-tiptop-blip-09ed@gregkh>
Hi Greg,
Thanks for your patch, which is now commit 6e90b675cf942e50
("MAINTAINERS: Remove some entries due to various compliance
requirements.") in v6.12-rc4.
On Fri, 18 Oct 2024, Greg Kroah-Hartman wrote:
> Remove some entries due to various compliance requirements. They can come
> back in the future if sufficient documentation is provided.
This is very vague...
What are "various compliance requirements"?
What does "sufficient documentation" mean?
I can guess, but I think it's better to spell out the rules, as Linux
kernel development is done "in the open". I am also afraid this is
opening the door for further (ab)use...
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
next parent reply other threads:[~2024-10-21 7:50 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 [this message]
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-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=a520d1f5-8273-d67e-97fe-67f73edce9f1@linux-m68k.org \
--to=geert@linux-m68k.org \
--cc=gregkh@linuxfoundation.org \
--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®