I've found a case where git apply --numstat and git log --numstat produce different results for the same commit. In egit (git://repo.or.cz/egit.git/): $ git log --numstat -1 --pretty=o 9bda5ece6806cd797416eaa47c 9bda5ece6806cd797416eaa47c7b927cc6e9c3b2 Teach RevWalk about ... 8 0 org.spearce.jgit/src/org/spearce/jgit/revwalk/DateRevQueue.java 69 13 org.spearce.jgit/src/org/spearce/jgit/revwalk/RevWalk.java $ git log -p -1 --pretty=o 9bda5ece6806cd797416eaa47c | git apply --numstat 8 0 org.spearce.jgit/src/org/spearce/jgit/revwalk/DateRevQueue.java 68 12 org.spearce.jgit/src/org/spearce/jgit/revwalk/RevWalk.java I found this because I was writing a unit test for JGit that ran through the JGit project history and compared the output of git log --numstat against the output of JGit's "git apply --numstat" implementation, after scraping the "git log -p" output. I can't quite figure out why log --numstat is coming up with a +1 difference here for both added and removed, but it is. I haven't dug into the Git code yet to figure out why. FWIW, JGit produces the same result as "git apply --numstat" (the 68/12). At this point JGit was able to successfully read and match 715 of 1211 commits before it found this difference, so its also somewhat rare to occur I think... -- Shawn. -- 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
