Conversation

Notices

1. Embed this notice
   Ron Gilbert, Esq. (grumpygamer@mastodon.gamedev.place)'s status on Friday, 10-Jan-2025 21:51:56 JST Ron Gilbert, Esq.

   I dislike git blame. It's hostile. It assume there is someone to blame. That someone did something wrong. That someone is at fault.

   • Embed this notice
     The Seven Voyages Of Steve (sinbad@mastodon.gamedev.place)'s status on Friday, 10-Jan-2025 21:51:55 JST The Seven Voyages Of Steve

     in reply to

     @grumpygamer They added "git annotate" later because of this, but "git blame" remains so as not to break old scripts

   • Embed this notice
     Juan (reidrac@mastodon.gamedev.place)'s status on Friday, 10-Jan-2025 22:08:10 JST Juan

     in reply to

     • The Seven Voyages Of Steve

     @sinbad @grumpygamer when I really got into git I think both were available already? I can't remember, but I write blame because old habits and is shorter and... I don't judge people (very often I find it was *me* anyway).

   • Embed this notice
     David (idbrii@mastodon.gamedev.place)'s status on Saturday, 11-Jan-2025 01:33:02 JST David

     in reply to

     @reidrac @sinbad
     Apparently annotate was first and blame was a different competing implementations:
     https://git.vger.kernel.narkive.com/XgwB2lTo/blame-vs-annotate#post4

     I'm not that familiar with git dev history, so I wonder if many of their features had rivals until one won and eliminated the other!

   • Embed this notice
     The Seven Voyages Of Steve (sinbad@mastodon.gamedev.place)'s status on Saturday, 11-Jan-2025 01:33:32 JST The Seven Voyages Of Steve

     in reply to

     • David
     • Juan

     @idbrii @reidrac huh, I always thought it was the other way around