"Jonathan del Strother" <maillist@xxxxxxxxxxxxxx> writes:
> What's the difference between 'git blame' & 'git annotate'? The
> output is practically identical - it's not obvious when you would use
> one over the other
In short, don't use git-annotate unless you are an ancient script that was
written before git-blame was written. They are functionally equivalent,
uses the same blame assigning engine, and the only difference is the
default output format, and blame knows how to mimick annotate output.
History.
The first implementation was called git-annotate that was implemented in
Perl.
c65e898 (Add git-annotate, a tool for assigning blame., 2006-02-20)
A competing implementation in C was done and was called git-blame:
cbfb73d (Add git-blame, a tool for assigning blame., 2006-02-21)
They competed for a while but it became more and more apparent that blame
was a better implementation. After blame learned to mimick annotate
output, which some scripts depended on, Perl implementation was retired,
but the name git-annotate was left as a backward compatibility alias:
f789e34 (Remove git-annotate.perl and create a builtin-alias for git-blame, 2006-10-09)
Then as an experiment, a reimplementation of blame in C, confusingly
codenamed git-pickaxe, was started, to detect code movements across and
within files:
cee7f24 (git-pickaxe: blame rewritten., 2006-10-19)
This had the same output format as git-blame, also with compatibility
output format implemented for the older git-annotate. After it matured,
it took over the original git-blame name.
acca687 (git-pickaxe: retire pickaxe, 2006-11-08)
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
