News for hackers. Stuff that matters.
Re:Yesterday, my program worked. Today, it does not. Why? (1... by devrandomguy on Wednesday July 19, 2017 @09:34AM (#14804140)
Git bisect is awesome. Before I discovered it, I was manually bisecting the codebase, and stubbing out the missing half.
Re:Yesterday, my program worked. Today, it does not. Why? (1... by adrianratnapala on Wednesday July 19, 2017 @09:49AM (#14804236)
Not to take away from git bisect (or hg bisect, which is no more broken than the rest of mercurial) -- I don't think it is an alternative to the thing you used to do.

git bisect is "temporal bisection", i.e. you delete half of a time interval. The manual bisect is kinda-sorta "spatial" in the sense that you delete half a region of code. the two things work by similar principles, and their problem domains overlap -- but they are not the same.

Re:Yesterday, my program worked. Today, it does not. Why? (1... by MaulingMonkey on Wednesday July 19, 2017 @07:32PM (#14808904)
They're complimentary techniques. One might git bisect down to the commit level, then manually bisect the sub-changes in the commit if it's a large one.

I've done the manual equivalent in perforce as well.