On Monday 2006 November 20 05:57, Alexander Litvinov wrote: > > PAGER=cat git log -M -C --pretty=oneline b/a I've come across this too. Personally I'm not sure what use "-C" is. From the manpage, man git-diff-files (no, this isn't the place I'd look either). --find-copies-harder For performance reasons, by default, -C option finds copies only if the original file of the copy was modified in the same changeset. This flag makes the command inspect unmodified files as candidates for the source of copy. This is a very expensive operation for large projects, so use it with caution. That is to say that unless the file you are copying was modified AND copied in the same commit, it won't be searched as a potential source for the copy operation. I think it would be rare to make a copy of a file I had modified, surely I'd want to check in modifications before making a copy? Regardlss, to get the results you want, use the stronger switch --find-copies-harder, heeding the warning that on big projects it will be very slow. Andy -- Dr Andy Parkins, M Eng (hons), MIEE andyparkins@xxxxxxxxx - 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