News for hackers. Stuff that matters.

A comment on Finding a kernel regression in half an hour with git bisect run (2018). Parent comment

Re:Finding a kernel regression in half an hour with git bise... by kawsper on Wednesday July 28, 2021 @08:01PM (#27991259)
If it is just reorganisation of project files then the fastest way to fix the bug would likely be to just revert the commits.
[ Parent | on HN ]
Re:Finding a kernel regression in half an hour with git bise... by alexeldeib on Wednesday July 28, 2021 @10:05PM (#27992013)
Consequently, this highlights why the first person may have an incentive to fix it: if their code gets reverted to fix the issue, they will definitionally be forced to rework it before they’re able to merge again.
[ Parent | on HN ]