@kernellogger @corbet @monsieuricon I only CC lkml when:
1. It's the mailing list for the subsystem (e.g. regulator),
2. The subsystem mailing list is rather obscure, or not archived on lore.
3. The patch fixes a serious issue or regression.
Conversation
Notices
-
Embed this notice
Geert Uytterhoeven (geert@society.oftrolls.com)'s status on Wednesday, 08-Nov-2023 10:44:41 JST Geert Uytterhoeven - Haelwenn /элвэн/ :triskell: likes this.
-
Embed this notice
Thorsten Leemhuis (acct. 1/4) (kernellogger@fosstodon.org)'s status on Wednesday, 08-Nov-2023 10:44:42 JST Thorsten Leemhuis (acct. 1/4) But is LKML still CCed on basically everything? I didn't check, but I got the impression that sometimes it's forgotten or omitted on purpise. If that is frequently the case I wonder if it would make more sense to create some kind of "automatically filled catch all list" that better serves the needs of those that like LKML how it is.
[if anyone things it's worth bringing this point to the discussion let me know]
-
Embed this notice
Jonathan Corbet (corbet@social.kernel.org)'s status on Wednesday, 08-Nov-2023 10:44:43 JST Jonathan Corbet On the radar: what is the linux-kernel mailing list for? @monsieuricon is suggesting that many or most patch postings be redirected to a separate list:
https://lwn.net/ml/ksummit-discuss/20231106-venomous-raccoon-of-wealth-acc57c@nitro/
I've not jumped into the conversation because I'm still trying to figure out what I think about it. I'm one of those people who actually reads over that list; the broad view it provides is helpful in both the LWN and documentation-maintainer roles. But it *is* painful to keep up with.
LKML has traditionally been the place you post patches to get them reviewed. If that's not its role anymore, what is it for?