After patch "revision.c: --full-history fix" (6631c73) I have this in git tree. I have _manually_ ( --abbrev=nr does not apply in this case) truncated to 7 chars the SHA to be more readable) $ git-rev-list --topo-order --parents --remove-empty HEAD -- builtin-add.c 021b6e4 93872e0 93872e0 3c6a370 3c6a370 e8f990b e8f990b f259339 f259339 0d78153 0d78153 b4189aa 283c8ee $ git-rev-list --topo-order --remove-empty HEAD -- builtin-add.c 021b6e4 93872e0 3c6a370 e8f990b f259339 0d78153 $ What it seems is that with --parents option two more spurious revs are printed out. This revs have nothing to do with builtin-add.c, the file is newer then both of them. I have tested with different files and always we have spurious revisions in case of files that were added after initial commit, and always the erroneous revisions are older then file creation one. This is a possible regression that breaks things (I've found it thanks to an assert in qgit). Marco - : 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