Oleksandr Natalenko, MSE 
oleksandr@natalenko.name
Could any sober soul explain it to me why this commit is qualified for a so-called "stable" kernel?
2
0
0
1
0
0
Oleksandr Natalenko, MSE
oleksandr@natalenko.name
@shironeko What about shrinking this to a minimally possible fix?
1
0
0
1
0
0
Oleksandr Natalenko, MSE
oleksandr@natalenko.name
@shironeko One doesn't have to merge 900 patches in one go in the first place.
1
0
0
1
0
0
Oleksandr Natalenko, MSE
oleksandr@natalenko.name
@shironeko Thousands of backports going into one release.
1
0
0
1
0
0
Oleksandr Natalenko, MSE
oleksandr@natalenko.name
@shironeko Just lets not apply what's not important ¯\_(ツ)_/¯.
1
0
0
1
0
0
Oleksandr Natalenko, MSE
oleksandr@natalenko.name
@shironeko Except regressions from excessive backporting, and that has to be patched by distro maintainers additionally.
1
0
0
1
0
0
Oleksandr Natalenko, MSE
oleksandr@natalenko.name
@shironeko Bleeding edge? Probably. But they are using a "stable" kernel that literally declares itself as such, which is a discrepancy between the name and what it actually is.
1
0
1
Sven Peter
sven@social.treehouse.systems@ljs @vbabka @oleksandr 🔮will this cleanup further improve the software development process? 💭
0
0
2
1
0
0