> From: Gergely Polonkai <gerg...@polonkai.eu>
> Now that we know this, git-bisect is exactly the tool he needs! He
> specifies the last known commit without the bug, and the first known commit
> with the bug. Git will then choose intermediate commits for you to test if
> the bug still exists, and point you to the first bad one.
Yes -- and git-bisect handles nicely the situation where the bug was
introduced not by the latest commit that affected the file in
question, but by some previous commit.
You received this message because you are subscribed to the Google Groups "Git
for human beings" group.
To unsubscribe from this group and stop receiving emails from it, send an email
For more options, visit https://groups.google.com/d/optout.