Getting closer and closer to the point where I'll start a git tree[1] with fixes and reverts for #Linux#kernel regressions in the latest stable series, as from here it seems quite a few of the known problems could quickly be solved by a revert or applying fixes already queued[2]/still under review[3].
And reg. that page: yup, but I guess there are always a few regressions I'm missing that @archlinux@fedora@opensuse kernel package maintainers are aware of; furthermore they are all in round about the same situation, so collaborating likely would make a lot of sense there.
Maybe to also expand on my other answer: We (Arch Linux) always encourage people to report upstream bugs to the relevant upstreams or help them debugging the relevant issues by providing them instructions or even prebuilt kernels for the bisection. If there is anything from your side that we could do better feel free to let us know!
2/ In case anyone wonders "why not simply fix the problems in upstream #Linux":
That would definitely be preferred! But in practise this often is anything but quick due to various reasons. Two of them:
Mainline developers are free to ignore stable #kernels and thus sometimes see no need to fix something quickly when the next mainline release is still weeks away.
The stable team only applies fixes that were mainlined and thus usually can not fix anything that occurs in mainline as well.
@kernellogger hot take, but I feel like the kernel community needs to be reminded of this more often :) Are you sure what you’re proposing isn’t a workaround for a tooling problem?
One of largest issues with the mailing list workflow is that it’s really hard to keep track of patches, they can’t be labeled and quickly get lost in the constant stream of new emails.
Yes, I'm sure that is not primarily a tooling problem, as the way bigger problem clearly is the workflow/motivation problem I mentioned ("Mainline developers […] see no need to fix something quickly"): different tooling alone would not make that go away (but of course with different tooling workflows also often get changed).
Add comment