Hi, Thank you everybody for your replies. I believe that this functionality would be useful; however, sadly my C skills are non-existent so I don't even know how to start looking at this problem. I don't suppose there are other developers on here that would be interested in having a look at this functionality? Thanks again, Albert -----Original Message----- From: git-owner@xxxxxxxxxxxxxxx [mailto:git-owner@xxxxxxxxxxxxxxx] On Behalf Of Linus Torvalds Sent: Saturday, 15 May 2010 1:29 AM To: Martin Langhoff Cc: Jeff King; Albert Krawczyk; git@xxxxxxxxxxxxxxx Subject: Re: Git log follow question On Fri, 14 May 2010, Martin Langhoff wrote: > > The use case for this is: "Where the hell does this WTF-worthy > function come from, in this WTF-esque old codebase I just inherited?" Umm. And git does that better than anything else. "git log --follow" works fine. As does "git blame -C". It's just that gitk does not, because it wants to show the graph. Anyway, if you feel strongly about it, and really want "gitk --follow", you really need to do it yourself. I gave you some pointers. I personally don't think it's worth it. Linus -- 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 -- 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