From: Alexander Litvinov Date: Mon, 20 Nov 2006 11:33:42 GMT Subject: Re: Rename detection at git log Message-ID: <200611201733.42723.litvinov2004@gmail.com> In-Reply-To: <7vejry5t4g.fsf@assigned-by-dhcp.cox.net> > What it means is that "git log" will look at path that matches > b/a (that means b/a/c and b/a/d are looked at, if b/a were a > directory). Since path "a" which is what the file was > originally at is not something the pattern b/a matches, there is > no way b/a is noticed as a rename from a. I have found that git blame show correct commits for this case. But I am still in trouble then examining file's history. I have found I can use git show -C -M commit-sha1 for commit there file was created to see if this was a rename :-)