- cross-posted to:
- [email protected]
- [email protected]
- cross-posted to:
- [email protected]
- [email protected]
The phoronix title is a bit click bait, but the LKML thread that is linked in the article is worth reading.
You must log in or register to comment.
This maintainer is pulling rank on those below him. He is causing people making good contributions to Linux to quit the project. Yet he cannot handle his own decisions being overridden and he is attempting to force his agenda by threatening to quit.
His says that he cannot abide by a mixed code base and that, if that is the way Linux goes, he will “spend his time doing something else”.
Well, the time for that argument was a while ago. It was already decided to make Linux a mixed code base. If this maintainer is saying that he cannot support this decision, he needs to go at some point. What makes him better than all the people he is causing to quit?
If Linus does let this stand, it is a total failure of leadership.
The Linux Project either needs to accept technically sound Rust contributions or it needs to acknowledge that it is abandoning its Rust experiment.
I wouldn’t correct you if this was a general community where the internet gantry hangs in numbers like the multiple !linux communities, but let’s keep things more factual here in !rust.
After Wedson quit months ago, no one from the Rust-For-Linux effort has quit/resigned/whatever. No one quit who is relevant to current mainline kernel development in general, either.
There is a difference between the actual Rust-For-Linux team, and Rust proponents who may write kernel code out-of-tree, or may happen to still be listed as maintainers in a dead poor GPU driver. Confusing the two is good for drama, but let’s not do that here.
And the bad boy maintainer is entitled to his opinion (which I disagree with of course). An opinion which will always be more informed and relevant than 99.999% of whatever the internet gantry has been contributing.
He is entitled to his opinion, he is not entitled to insult people because of that though and he should not be allowed to influence the course of the project as a whole in this major way if he couldn’t even be arsed to bring his opinion when everyone else was having that discussion three years ago.
The response by Greg KH is also well worth reading:
https://lore.kernel.org/rust-for-linux/2025021954-flaccid-pucker-f7d9@gregkh/
Indeed, it’s very good. I wish he had send this before 2 Rust maintainers resigned, but I assume that he did not want to undercut Linus decisions.
After that response, I wish he was in charge of the project.
I think Larabel was a bit too quick to publish on this one. It was later clarified in the thread that Linus would not merge rust against maintainers’ will.
Do you have a link to that?
The document does not claim Linus cannot override maintainers anymore. That can happen for anything, as you very well know. But I think everyone agrees that it shouldn’t come to that – at least I hope so.
1st reply to the email from Miguel Ojeda. Same thread as Greg KH’s reply.
How dare you change the click-bait title❓
I mean, it’s a moronix post. No one was expecting some serious reporting anyway🙂
Otherwise, you could have just pointed to the mailing list thread directly (preferable).Yes, but then you wouldn’t find the comment section there to read all the insightful comments… /s
True. Moronix’s comment section is always good for a good laugh. Although the novelty wears off fast due to the lack of novelty/originality.
