3 ms·
You could have editorialized this title to: Rebasing a Linux Kernel Branch that’s Two Years Old and 9k Commits Deep …but you would have had thousands of us ru
by gorgoiler 5y ago
You could have editorialized this title to:
Rebasing a Linux Kernel Branch that’s Two Years Old and 9k Commits Deep
…but you would have had thousands of us running to the bathroom to revisit our last meal.
What a Herculean effort by these two engineers. When your role is to track down fellow employees from completely different teams and crack the, er, carrot to get them to update their patch from two years ago, you can get very tired very quickly.
I’m sure the hardware driver modules are fairly self contained but things like the userspace QoS patch could be pretty hairy. The kind of thing where, for upstream, you’d spend 90% of your time landing a framework just to even be able to implement your feature with the final 10% patch.
Oof. Bravo.
- lt 5y agoAs far as I understood, your editorialized title is what they've been doing every two years since ever. A possible better editorialized title would be Creating a parallel kernel so we can continually rebase commits instead of every two years
- Too 5y agoDon't forgot the part where the author of the patch left the company a year ago, or even worse the entire team got dissolved/reorganized, which tends to happen quite regularly in a bigco. No amount of carrots will help there I'm afraid. Herculean effort indeed.
- menage 5y ago> The kind of thing where, for upstream, you’d spend 90% of your time landing a framework just to even be able to implement your feature with the final 10% patch. I feel this was a fair description of CGroups.