Hi, I just tried to find out when certain changes percolated into log-tree.c. So I issued "git log --cc next log-tree.c". Wonders of wonders, the patches did not contain *anything* about what I tried to find, even if the file contains the key words. Because the path limiting is overeager (I finally found what I looked for in commit f4235f8b): git-name-rev $(git-rev-list --pretty=oneline \ f4235f8b2ef875b85ead74ffa199d827f9ee9d8d..next log-tree.c | \ sed "s/ .*$//") yields cb8f64b4e3f263c113b7a2f156af74b810e969ff next^2 cd2bdc5309461034e5cc58e1d3e87535ed9e093b next~10^2~2 while without path limiting, git-name-rev $(git-whatchanged.sh --pretty=oneline \ f4235f8b2ef875b85ead74ffa199d827f9ee9d8d^..next log-tree.c | \ sed -n "s/^diff-tree \([^ ]*\).*$/\1/p") I get cb8f64b4e3f263c113b7a2f156af74b810e969ff next^2 c5ccd8be43df4b916752a176512a9adaf3b94df9 next~4^2 f4235f8b2ef875b85ead74ffa199d827f9ee9d8d next~6^2 183df63940bf92ea626af64d0057165b8aad24f6 next~8^2 cd2bdc5309461034e5cc58e1d3e87535ed9e093b next~10^2~2 I am not intelligent enough to find out why there are three revisions which get culled. Ideas? Ciao, Dscho - : 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