Junio, I am resending this one because I am not sure whether you ignored it on purpose, or it got lost during your vacation. The combination of -m and --with-tree shows duplicate entries: and@dylle:~$ mkdir repo ; cd repo and@dylle:~/repo$ git init Initialized empty Git repository in /home/and/repo/.git/ and@dylle:~/repo$ date >a ; git add a ; git commit -m'Add 1' Created initial commit c027435: Add 1 1 files changed, 1 insertions(+), 0 deletions(-) create mode 100644 a and@dylle:~/repo$ date >a and@dylle:~/repo$ git ls-files -m --with-tree=HEAD a a Jeff King added: I have confirmed this, and it looks like it has always been that way. It looks like overlay_tree_on_cache just does a read_tree to pull the tree into the index, and then we end up with duplicate entries. I'm not too familiar with the read_tree code, so I am cc'ing Junio (who is out of touch for a little while) and Linus, who are much more clueful in this area. It isn't clear to me which code is _supposed_ to be pulling out such duplicates here. That is, is read_tree broken, or is overlay_tree_on_cache just calling it wrong? Anders. -- 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
