News for hackers. Stuff that matters.
Re:Yesterday, my program worked. Today, it does not. Why? (1... by azhenley on Wednesday July 19, 2017 @09:45AM (#14804206)
This is awesome. Didn't know about it, thanks!

My approach has been to step exponentially. I go back 1 commit, 2 commits, 4 commits... etc. I'll be using bisect from now on though.

Re:Yesterday, my program worked. Today, it does not. Why? (1... by pishpash on Wednesday July 19, 2017 @10:58AM (#14804743)
You may be implementing an intuitive weighted bisect :)
Re:Yesterday, my program worked. Today, it does not. Why? (1... by maccard on Wednesday July 19, 2017 @12:17PM (#14805410)
Heh, I do a binary search. Find last known good build, go half way between, etc
Re:Yesterday, my program worked. Today, it does not. Why? (1... by muxxa on Wednesday July 19, 2017 @03:24PM (#14807111)
I wish git bisect could handle the 'find last good build' step by jumping back exponentially through history, then switching to binary search once the last good build is found
Re:Yesterday, my program worked. Today, it does not. Why? (1... by ChronosKey on Wednesday July 19, 2017 @12:26PM (#14805478)
That's what git bisect does
Re:Yesterday, my program worked. Today, it does not. Why? (1... by maccard on Thursday July 20, 2017 @03:21AM (#14810606)
And not everyone uses git, unfortunately.
Re:Yesterday, my program worked. Today, it does not. Why? (1... by mcintyre1994 on Wednesday July 19, 2017 @12:27PM (#14805481)
This is what git-bisect does :)