Hacker News new | ask | show | jobs
by tmd83 3932 days ago
While the name maybe a bit unfortunate or maybe made just for fun, git blame has actual use. While it's useful to see the commit log and figure out how the bug came to be, it can also be useful to talk with the respective developer if available and get an even better perspective.
2 comments
LeoNatan25 3932 days ago
Indeed, but this is a different thing entirely. Getting a perspective to a problem and working together to fix it is one thing, going and pointing fingers, even in playful manner, is different. In the long run, it creates an unpleasant work environment.

In our office, I always take the blame jokingly to lighten the mood. It's a running gag, we have three people who are more senior than the others, and we always say "it's his fault, and if not, it's the other one and if not, then it's Leo's fault" (I am the most senior). When a problem arises, it doesn't matter who inserted the bug, but how to fix it the quickest.

link
icelancer 3932 days ago
You can just also use git annotate if you want to avoid the negativity.
link
tmd83 3932 days ago
Yup, wasn't defending this one :). Did the git annotate came after blame cause in the olden time I remember seeing the git blame example.

These days I mostly use IDEA's annotate feature and don't even know what's the command used in the backend.

link
bazzargh 3932 days ago
They both came from the earlier `cvs annotate` command. annotate is the original name (from 1996). While it was common to talk about cvs annotate as 'blame', I think it first became the name of a command in subversion 0.32.0 (~2003, rcs blame was ~2004, cvs annotate grew the blame alias ~2008)
link
bbatha 3932 days ago
Subversion has blame, praise, and annotate depending on your mood. [1] Though I think blame was first.

[1] http://svnbook.red-bean.com/en/1.6/svn.ref.svn.c.blame.html

link