We are the "thin blue line" that is trying to keep the code high quality
1–10 of 186 posts
Re: We are the "thin blue line" that is trying to keep the code high quality
#2[deleted]
Re: We are the "thin blue line" that is trying to keep the code high quality
#3why 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
Re: We are the "thin blue line" that is trying to keep the code high quality
#4Calling yourself the “thin blue line” like a reference to police really doesn’t seem like a way to have an enduring community. Police don’t serve the community; I guess they think in the same way then.
Re: We are the "thin blue line" that is trying to keep the code high quality
#5Calling yourself the “thin blue line” like a reference to police really doesn’t seem like a way to have an enduring community. Police don’t serve the community; I guess they think in the same way then.
Police in your area maybe?
Re: We are the "thin blue line" that is trying to keep the code high quality
#6Re: We are the "thin blue line" that is trying to keep the code high quality
#7why 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
marcan addresses this argument in an adjacent thread:
> Out of tree doesn't work. People, both in the kernel and out of the kernel, want things in tree.
https://lore.kernel.org/lkml/1e8452ab-613a-4c85-adc0-0c4a293...
Re: We are the "thin blue line" that is trying to keep the code high quality
#8not the phrase I'd choose to associate with, even metaphorically
Re: We are the "thin blue line" that is trying to keep the code high quality
#9The problem is aging code sours like milk.
I empathize but we need to have people take over these initiatives and refactor them into something easier the maintain. Not saying introduce a new language or anything but change how we fundamentally look at “The Kernel”. I think reducing scope and making it so hardware providers must maintain their drivers is a good start. If your toolchain doesn’t suffice, create a new tool.
If rust is so much better, create a new kernel in rust and force a paradigm shift. I think we can do better than bicker and fight over it and post email chains about it. Bring solutions. Tech debt is just OpEx to everyone else.
Re: We are the "thin blue line" that is trying to keep the code high quality
#10why 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
There are still a few custom kernels out there. Liquorix comes to mind.