On 10/22/07, Federico Mena Quintero <federico@xxxxxxxxxx> wrote: > On Mon, 2007-10-22 at 09:59 +0200, Andreas Ericsson wrote: > >> I doubt many people on this list regularly use git-blame but it's a >> command that's definitely non-trivial to script out using only the >> "proper" commands, and CVS/SVN users expect it to be there, so it's >> probably worth listing anyhow. > Personally I find git-blame *EXTREMELY* useful. The workflow is: > 5. "WTF? Who wrote this crappy code?" > > 6. git blame culprit-file.c > > 7. "Oh, it was $person with $commit_id... what were they thinking at the > time?" > > 8. git show $commit_id You don't need blame for that (by the way, as git-blame is slow, you can try -L option to limit range of lines; it is a pity that 'git gui blame' does not support it yet). You can use 'pickaxe search', i.e. "git log -S'<crappy code>'". Sometimes it is better than git-blame... -- Jakub Narebski - To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
