Hacker News Reader

Comment by p0w3n3d | Hacker News Reader

Things I'm missing in git are not how many lines or commits given developer did, which might lead in a poorly managed organisation to strangely calculated KPIs, but rather:

  - who deleted this line (which one?)
  - who is owner of this method (some guy refactored it or reformatted, but who is the REAL owner, or what was the history of this method)

View on HN

> - who is owner of this method (some guy refactored it or reformatted, but who is the REAL owner, or what was the history of this method)

It doesn't work perfectly, but with magit you can jump to the revision before the refactor/reformat, then do another blame from there. I chased a line of code through several layers of refactors that way before and while the original author was long gone it did help explain why things were initially done that way.

I heavily depend on git-blame to understand code. It's one reason why I generally dislike "cleanup" changes that just change formatting/naming for the sake of it.

Yes, exactly.

That is what I use git for each and every day.

Reply on news.ycombinator.com