Junio C Hamano writes: > Paul Mackerras <paulus@xxxxxxxxx> writes: > > > There are times when gitk needs to know that the commits it has sent > > to git-diff-tree --stdin did not match, and it needs to know in a > > timely fashion even if none of them match. At the moment, > > git-diff-tree outputs nothing for non-matching commits, so it is > > impossible for gitk to distinguish between git-diff-tree being slow > > and git-diff-tree saying no. > > Wouldn't this help? > > $ git-diff-tree --stdin --always On the git.git tree: $ cat revs 65aadb92a1ce9605fa2f412b51de91781a3ef3d6 cc189c2ca2c725c430f100f61e7c4a6849f93163 $ git diff-tree -r -s --stdin -- apply.c <revs 65aadb92a1ce9605fa2f412b51de91781a3ef3d6 $ git diff-tree -r -s --stdin --always -- apply.c <revs 65aadb92a1ce9605fa2f412b51de91781a3ef3d6 cc189c2ca2c725c430f100f61e7c4a6849f93163 $ With --always, how do I tell that 65aadb affects apply.c and cc189c doesn't? Paul. - : 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