Junio C Hamano <gitster@xxxxxxxxx> writes: > "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. Then, does it make sense to apply this? --- a/Documentation/git-annotate.txt +++ b/Documentation/git-annotate.txt @@ -14,6 +14,10 @@ DESCRIPTION Annotates each line in the given file with information from the commit which introduced the line. Optionally annotate from a given revision. +This command exists for backward compatibility. If you don't have +existing scripts using 'git annotate', you should use +linkgit:git-blame[1] instead. + OPTIONS ------- include::blame-options.txt[] -- Matthieu -- 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
