"Anders Melchiorsen" <mail@xxxxxxxxxxxxxxxx> writes: > and@dylle:~/repo$ git ls-files -m --with-tree=HEAD > a > a > > > Jeff King added: > ... > 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? I had to look up what -m meant in ls-files, as I never considered that option as part of the plumbing. What's the use case of using -m together with --with-tree to begin with? I think the only sensible other option that makes sense with --with-tree is --error-unmatch. -- 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