Huge, huge thanks to git bisect! With its help, I …

Huge, huge thanks to git bisect! With its help, I just sorted out a huge argument about who removed a piece of code and when.  With an actively developed project among few developers and branches, it’s not trivial to say when the change was introduced.  Unless, of course, you are using git bisect.  Every developer should know how to use it.

3 thoughts on “Huge, huge thanks to git bisect! With its help, I …”


  1. git bisect is awesome

    If you know what you’re looking for (and in which file), you might also be able to use a more verbose version of git log:

    git log –follow -p [file] | less -i

Leave a Reply to Zakhar Kirpichenko Cancel reply