Hacker News new | ask | show | jobs
by TZubiri 452 days ago
No. You are thinking of git bisect
2 comments

Bisect shows which commit is responsible for a yes/no behavior change. Blame shows which commit is responsible for a line of code. Both are useful for finding the responsible commit but for different things.
No, bisect is not blame but for commits. Blame shows you which COMMIT is to blame. That's my point.
True

Git log gives the author (et al) given a commit.

Git blame gives the commit given the line and file.

Worth noting that annotate and praise were added to address the semantics, regardless of whether they were the original intent or not