News for hackers. Stuff that matters.
Re:The Git history command deserves more attention by efilife on Monday July 13, 2026 @11:25PM (#48901911)
Didn't you mean "dissecting"?

Edit: thanks guys, that's very useful knowledge! Could have saved me many times in the past

Re:The Git history command deserves more attention by psadauskas on Monday July 13, 2026 @11:32PM (#48901962)
Nope, `bisect`: https://git-scm.com/docs/git-bisect

Figure out a command to test it, a known-good sha and a known-bad sha, and it will binary search its way through the history to find the commit that introduced the failure.

Re:The Git history command deserves more attention by seba_dos1 on Monday July 13, 2026 @11:28PM (#48901931)
Check out "man git-bisect".
Re:The Git history command deserves more attention by jolmg on Monday July 13, 2026 @11:27PM (#48901930)

  man git-bisect