On 02/18/2012 08:53 AM, Andreas Färber wrote: >> I think only 'git blame' output would be affected and that is not 100% >> reliable anyway, considering for example code movement. > > I use repo.or.cz's blame function quite often to find out who to cc or > what commit to mention, and (valid) typo fixes are already troublesome, > requiring to go to the parent commit and to navigate to the same file in > its tree. One cannot specify any custom ignore options there. > > Is there a better tool to do such interactive, recursive git-blame?
I use 'git gui blame $commit $file &' for interactive recursive blaming. When you find the line that you are interested in blaming, you can click on the commit link on the left side to see the context at the time of the commit that introduced the state of that line, then right click on the right side (the line in question) to easily trigger a 'blame parent' operation. It's about the only thing that I use 'git gui' for, but I find it well worth the pain of using a tcl frontend. -- Eric Blake ebl...@redhat.com +1-919-301-3266 Libvirt virtualization library http://libvirt.org
signature.asc
Description: OpenPGP digital signature
