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. Hmmm, I don't really want to turn the "summary" thread into oodles of sub-threads, but here goes :) Personally I find git-blame *EXTREMELY* useful. The workflow is: 1. Bug #12345 for FooApp gets assigned to you. 2. git-svn clone fooapp's repository 3. git checkout -b my-bugfix-branch-for-12345 4. debug debug debug 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 9. "Oh, I see their intentions now... what was going on at that time?" 10. git log <date range around $commit_id> 11. etc. Git-blame is very nice for code archaeology (long explanation at http://mail.gnome.org/archives/desktop-devel-list/2007-September/msg00238.html). > Similarly, it might be helpful to have help topics the gdb way, like > "git help patches". This would be simply fantastic. If those help topics suggested workflows, I'd be delighted :) Feel free to poke me if you write up some text; I'd love to help on this. Federico - 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
