fosstodon.org is one of the many independent Mastodon servers you can use to participate in the fediverse.
Fosstodon is an invite only Mastodon instance that is open to those who are interested in technology; particularly free & open source software. If you wish to join, contact us for an invite.

Administered by:

Server stats:

10K
active users

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?
lwn.netRFC: switching "THE REST" in MAINTAINERS away from linux-kernel@vger.kernel.org [LWN.net]

@corbet @monsieuricon

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]

@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.

Thorsten Leemhuis (acct. 1/4)

@geert @corbet @monsieuricon

yeah, make sense (side note: CCing the regressions list on regression would be nice, too). And I got the impression a few people use a similar strategy, but I didn't properly check.