{"thread":{"id":"20789","subject":"Strangeness with git log --follow","startedAt":"2009-08-30T14:31:54Z","lastAt":"2009-08-30T14:31:54Z","messageCount":1,"participants":["Brenton Fletcher"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"122115","messageId":"E50B7EBE-7DBB-442F-A341-FD8A1EEFB41B@bloople.net","threadId":"20789","inReplyTo":null,"subject":"Strangeness with git log --follow","fromName":"Brenton Fletcher","fromEmail":"i@bloople.net","sentAt":"2009-08-30T14:31:54Z","receivedAt":"2009-08-30T14:31:54Z","isPatch":false,"sender":{"key":"i@bloople.net","avatar":null},"body":"I'm using git log --follow -p <filename> to list all the commits  \naffecting a certain file. My problem is that git log --follow --topo- \norder returns fewer commits than git log --follow --date-order (or  \ndefault). The docs for git log and git-rev-list don't seem to indicate  \nwhay this is happening.\n\nThe repo I'm working with is http://github.com/bloopletech/keycontrol/tree/master \n  and the file is original/C/kc.c on the master branch; I'm using git  \nv1.6.4.2\n\nAm I misunderstanding what's going on here? --topo-order is kind of  \ndoing that I want since it's generating a nice series of commits that  \ndiff against each other nicely, whereas running without topo-order is  \nreturning the commits in a sequence which means thay don't properly  \ndiff against each other. I like the results I'm getting from --topo- \norder, but I need results in date order, which is not assured AFAIK  \nwith topo-order.\n\nIf someone could enlighten me as to what's going on, thanks!\n\n-Brenton Fletcher\n"}]}