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 bdavis__ on Wednesday July 28, 2021 @09:17PM (#27991719)
this isn't blame. you broke it, you fix it. this is how people learn from mistakes. do you ridicule the person? absolutely not. does it belong to the team? absolutely. But, you broke it, you fix it. See also, "Pottery Barn Rule"
[ Parent | on HN ]
Re:Finding a kernel regression in half an hour with git bise... by hortense on Thursday July 29, 2021 @06:04AM (#27994702)
On large codebases that does not hold because you can't expect everybody to know all the code and how it should behave. If you broke it but there was no test, it's not your fault.

"if you liked it, then you should have put a test on it".

[ Parent | on HN ]