Live data from Hacker News

We are the "thin blue line" that is trying to keep the code high quality

lore.kernel.org

181–186 of 186 posts

Re: We are the "thin blue line" that is trying to keep the code high quality

#181

Earlier quoted context omitted.

[flagged]

It's surreal how some people can go from "thin blue line" to swastika in a micro-second. What the f is going on here? Where are you pulling this crap from? haha.

It's the "everyone I don't agree with is a literal nazi" mindset.

Re: We are the "thin blue line" that is trying to keep the code high quality

#182
post #88

Earlier quoted context omitted.

Bro, just don't rob CVS

Also don't ever jog down the street. In fact, don't even sleep inside your own home!

That's a uniquely American problem, not one inherent to the economic model.

Re: We are the "thin blue line" that is trying to keep the code high quality

#183

More shots fired at Linus (justifiably so) https://lore.kernel.org/lkml/6e3e26c7-002a-49c6-a3a8-1cc1b89...

"Shots fired" from a random anonymous person? Everyone can send their rant to LKML, that doesnt mean anything.

Re: We are the "thin blue line" that is trying to keep the code high quality

#184
post #3

why cannot more people learn about git and branching you want your merges in? patch it in your own branch the real crux of the issue is the quality of " the offical version", the real issue, then, is about official branding. I remember back in the day there were multiple kernel versions by different mantainers.... then again I'm probably missing the forest for the trees or something

Because forked kernels is how we ended up with all those SBCs which could only run some ancient version of linux. If you can't mainline it, you are committing to maintaining a fork forever, and the more changes you require, the more maintenance that fork will be. The Linux kernel quite intentionally makes maintaining a fork a pain in the ass to pressure vendors to mainline their drives. But now mainline maintainers a…

But the Rust advocates are already telling everyone that they will handle all maintenance of rust code in the kernel and existing maintainers won't have to do a thing. If that was true it wouldn't matter if the rust code is in a separate tree.
Post reply on HN