Ramkumar Ramachandra wrote: > $ git log README.md > > What do you expect? The same output you would get if you cloned > gh:artagnon/clayoven separately and executed 'git log README.md' on > it.
And the reason I brought up rev-parse in the first place is because this problem is not unique to log. Try a 'git shortlog README.md' if you're not convinced. The entire revision-walking-pathspec-filtering mechanism in the log-like-family is broken on trees that are read into a non-/ prefix. And no, it doesn't have anything to do with renames or "rename detection". If it did, 'git shortlog README.md' should atleast give me the commit that was responsible for the rename. And if you're still wondering about --follow, 'git shortlog --follow' (undocumented) is completely broken. -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
