5 ms·

I liked this one: git blame -w Ignore the whitespace if a block was [un]indented, attribute to original author instead of person re-indenting due to contr

I liked this one: git blame -w Ignore the whitespace if a block was [un]indented, attribute to original author instead of person re-indenting due to control structure change around block.

masklinn 13y ago
The truth is that command-line blame is a pain in the ass. Blame is great for finding out where a piece of code comes from, but (especially on big projects with many contributors) there's a lot of small churn with code being moved around, slightly altered, etc… CLI blame requires an extensive danse of "blame to find out last change before $(rev:tip)" "log with patch to find out if it's the change I'm looking for" "get previous revision", rinse and repeat until step 2 yields a match. And for all the GUIs available, most of them either don't even touch blame, or just return the output of the CLI blame command. The only GUI I've seen so far which makes it easy to traverse history through blame is for bazaar (qblame/qannotate).
- davvid 13y ago
  `git gui blame` is actually pretty great. You can click around to parent commits and everything.
- nicwolff 13y ago
  tig's blame is great, cursor through the file to any line and hit B to jump the whole file back in time to the last previous commit that changed that line; repeat as needed.
- Stratoscope 13y ago
  SmartGit/Hg has a great interactive blame display. You can hover over commits to see the commit message, click on them to go back, etc. If you put the focus on the "View commit" select, then you can use the up and down arrows to go through the commits. You can also select different previous commits for the comparison window. Very easy to use and flexible. IntelliJ IDEA also has a pretty nice blame panel. It's not as full-featured as SmartGit, but it's right there in the editor for any file with a quick Alt-G-N. I would definitely recommend trying out SmartGit.

I liked this one: git blame -w Ignore the whitespace if a block was [un]indented, attribute to original author instead of person re-indenting due to control structure change around block.

masklinn 13y ago

The truth is that command-line blame is a pain in the ass. Blame is great for finding out where a piece of code comes from, but (especially on big projects with many contributors) there's a lot of small churn with code being moved around, slightly altered, etc… CLI blame requires an extensive danse of "blame to find out last change before $(rev:tip)" "log with patch to find out if it's the change I'm looking for" "get previous revision", rinse and repeat until step 2 yields a match. And for all the GUIs available, most of them either don't even touch blame, or just return the output of the CLI blame command. The only GUI I've seen so far which makes it easy to traverse history through blame is for bazaar (qblame/qannotate).

davvid 13y ago
`git gui blame` is actually pretty great. You can click around to parent commits and everything.
nicwolff 13y ago
tig's blame is great, cursor through the file to any line and hit B to jump the whole file back in time to the last previous commit that changed that line; repeat as needed.
Stratoscope 13y ago
SmartGit/Hg has a great interactive blame display. You can hover over commits to see the commit message, click on them to go back, etc. If you put the focus on the "View commit" select, then you can use the up and down arrows to go through the commits. You can also select different previous commits for the comparison window. Very easy to use and flexible. IntelliJ IDEA also has a pretty nice blame panel. It's not as full-featured as SmartGit, but it's right there in the editor for any file with a quick Alt-G-N. I would definitely recommend trying out SmartGit.