this is the one and only reason that the Linux kernel is going out of its way to hide which commits are LLM generated by abolishing the Assisted-By tag, simultaneously with torvalds fully slopcoding a core “improvement” to the kernel’s memory management

if you don’t believe me, here’s part of what the diff removed from the kernel’s docs:

> -When AI tools contribute to kernel development, proper attribution
> -helps track the evolving role of AI in the development process.
> -Contributions should include an Assisted-by tag in the following format::

and surprise, here’s the dickheads responsible: en.wikipedia.org/wiki/Linux_Ke a set of people who get money and tokens from Anthropic, OpenAI, and a bunch of other AI corps via the Linux Foundation

don’t you love when the paid heads of a community project meet behind closed doors to do something that damages the community? furs.social/@Rycochet/11743896

en.wikipedia.org/wiki/Linux_Kernel_Developers_Summit

Replying to @⁨zzt@mas.to⁩

I’m pushing this reply to top level because it’s extremely important: is.badat.dev/objects/a142a17d-

> I asked whether that risked cutting off bright new developers that we would rather hang onto; Torvalds answered that the kernel project only wants serious developers. That includes having access to enough resources to function in this world.
> [...]
> Torvalds added that he does not want to scare off people who want to write code; his message is that you have to either put in the effort to learn, or put a lot of money into an LLM to participate.

Linus Torvalds prefers if you can’t contribute to the kernel without pouring money into tokens for Claude Code

if you don’t pay a shit ton of money for tokens, you aren’t a serious developer according to him

the “learn” thing here is a distraction: in this context, you’ll be learning to clean up slop until you either burn out (very quickly at that) or pay for tokens and cognitively surrender to the bot

that’s the learning path now

is.badat.dev/objects/a142a17d-9320-4007-bef4-99762f9fa854

Replying to @⁨zzt@mas.to⁩

@techokami > Laurent Pinchart said that some developers are frustrated that they have to justify their work against criticisms from Sashiko while other, LLM-generated patches appear to be accepted immediately. Abeni defended the automated reviews, though, saying that the number of patches introducing bugs has dropped considerably. Zijlstra said that, while reading LLM-generated reviews "shuts my brain down", he still thought that the tool is useful; it finds real problems.

fucking amazing

Replying to @⁨zzt@mas.to⁩

@techokami sashiko is their weird anthropomorphizing name for the LLM that runs on their CI and generates lists of “problems” with patches by the way, a thoroughly worthless thing in my long experience

as with all other systems like this, it thinks LLM code is a-ok but nitpicks code written by people to death

this is one of the mechanisms that burns you out fast when a project goes in on LLMs

en