On Wed, Mar 02, 2011 at 04:15:45PM -0500, Jeff King wrote: > On Wed, Mar 02, 2011 at 03:43:42PM -0500, Jez wrote: > > > Git-blame is useful, but sometimes I want to know the series of > > commits that have affected a line -- not just the most recent one. Is > > there a way to do this? > > If you use "git gui blame" or "tig blame", both have a "blame from > parent commit" feature. This restarts the blame using the content as it > was just before the answer you just got, so you can recursively dig. > It's unfortunately a somewhat manual process. > Hm. I guess pressing 'B' will blame the parent commit in tig. But I can't figure out how to navigate back to the old commit (before pressing 'B')? Any hints appreciated! -Peter -- 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