3 ms·
Linus unloads on the guy who did a pretty good job explaining what was in there (not why it was needed though), serves out plenty of collateral damage for every
by khaki54 4y ago
Linus unloads on the guy who did a pretty good job explaining what was in there (not why it was needed though), serves out plenty of collateral damage for everyone who's ever submitted a self-serving merge to go "hmm is he talking about me from 2 years ago?".
Despite making a good point, where the guy is thinking "well I guess I'm not getting that merge", he goes ahead and approves without further comment.
Probably controversial, but you want a few people like this in your organization holding the line against the barbarian hordes, especially when you are the barbarian, because you are reminded WHY you are following the process and it lets you know that others aren't getting over.
- temp2022account 4y agoI think Linus is making a good point, in a project as long-running as the kernel having commit messages like "Merge temp-branch-a into temp-branch-a-next" is clutter and really ought not make it into `master`. Obviously Linus could just manually re-merge the changes, picking out the commits individually, but that's a ton of work and doesn't scale well as contributors grow.