who called it `git blame` and not `git whose-line-is-it-anyway`?
@poss_bot I am *not* sorry
@ticky *BZZZZZT*
*BZZZZTBZZZZZTBZZZZZZZZZZZZZ*
elsewhere, @ticky provided a link to the origin of git-blame, (which is /not/ Linus) https://github.com/git/git/commit/cbfb73d73f272f194bafa70d5be1f35abc265c79
so there used to be a git-annotate, but this was merged.
@ticky CVS called it "annotate". SVN called it "annotate" and introduced 2 aliases: "blame" and "praise". Later on CVS grew a "blame" alias as well (in version 1.12).
Mercurial uses "annotate" with alias "blame" like CVS.
Git calls it "blame" with "annotate" as an alias which exists "for backwards compat" 
I wish git had called it just "praise".
@stsp mate it’s a joke, you don’t need to explain the history of the thing, it is a joke
@ticky Apologies, I didn't mean to barge in.
I honestly saw a question where there was none 
@deejoe cmon man clearly this is a joke
@deejoe did you consider that in your decision to post a reply to it?
I'm sorry it didn't work for you.
@deejoe we were using 110/300bps modems. A fifteen character command took a half second to TRANSMIT. And the core (yes core) memory was measured in kilobytes. Short names mattered.
@ticky too many characters
@charizard it’s? a joke?
@ticky new contender for my favourite best possible git command name, beating out my old custom script of "git onwithit"
git-onwithit, for the curious, is used to add all changed files and continue with the current rebase/merge/revert/whatever
https://github.com/chao-master/bin/blob/master/git-onwithit
@ticky well, now i'll probably never forget what `git blame` does
@ticky i can’t believe you’ve done this