3 ms·
When I say "code archeology", I mean the equivalent of "git blame" without assigning blame - just finding out why stuff is the way it is and not who's responsib
by pilif 12y ago
When I say "code archeology", I mean the equivalent of "git blame" without assigning blame - just finding out why stuff is the way it is and not who's responsible because that would be totally pointless, especially years after the incident.
I do like your spin however :-)
- gh02t 12y agoOh yeah, I knew your meaning. Doing blame and bisect to find a deep-seated bug can be a lot of fun... or frustrating and miserable. I tend to give terrible on word commit messages when I'm developing, but I always do an interactive rebase to clean things up and make a reasonable view of history. We use Phabricator a lot too, which does a great job of letting you annotate code, commits etc.
- NickNameNick 12y agoPraise is a built-in alias for SVN, not so for git unfortunately.
- icebraining 12y agoDitto in Bazaar, which copied SVN. But there's an easy fix: git config --global alias.praise blame