Hi, DragonFly BSD uses git as its SCM, with one single repository and branch for both the kernel and the whole userland. On 2011-11-26 (1322296064), someone did a commit that somehow touched every single file in the repository, even though most of the files were not modified one bit. That's the offending commit from 2011-11-26: http://gitweb.dragonflybsd.org/dragonfly.git/commitdiff/86d7f5d305c6adaa56ff4582ece9859d73106103 https://github.com/DragonFlyBSD/DragonFlyBSD/commit/86d7f5d305c6adaa56ff4582ece9859d73106103 Since then, with some tools, if you look at file history for any file anywhere in the repo, you can see that all files were changed on 2011-11-26 with that commit, but it's only shown in some tools, and not shown in others. For example, the bogus 2011-11-26 commit is not shown with the following: * git log sys/sys/sensors.h * https://github.com/DragonFlyBSD/DragonFlyBSD/commits/master/sys/sys/sensors.h However, the bogus commit is [erroneously] shown with the following: % git whatchanged --pretty=%at sys/sys/sensors.h | cat 1322296064 :000000 100644 0000000... 554cfc2... A sys/sys/sensors.h 1191329821 :000000 100644 0000000... 554cfc2... A sys/sys/sensors.h % Notice how the file was ]A]dded once again at 1322296064 without ever being deleted, and that the dst sha1 is the same for both the latest and the immediately prior revision of the file. Gitweb, unlike github, would also show the erroneous commit from 2011-11: http://gitweb.dragonflybsd.org/dragonfly.git/history/HEAD:/sys/sys/sensors.h Another, more representative example, which shows that src sha1 (field names are documented in git-diff-tree(1)) is always "0000000..." in such bogus touch-all commits (even though it makes little sense when you consider that the files were never deleted and still have the same dst sha1): % git whatchanged --pretty=%at sys/sys/sysctl.h | head -9 1322296064 :000000 100644 0000000... 6659977... A sys/sys/sysctl.h 1296826445 :100644 100644 94b8d96... 6659977... M sys/sys/sysctl.h 1292413105 :100644 100644 8c9deaa... 94b8d96... M sys/sys/sysctl.h % So, my questions are as follows: * How was it possible for all these files to be added without first being deleted in the first place? Was / is it a bug in git (during a commit) to allow something like that? * Why do some tools compact such bogus commits out (and hide them from the user), but some don't? * Is there a way to make git-whatchanged and gitweb ignore such bogus commits on files that weren't actually modified, just as git-log and github already do? P.S. I've asked this question on http://stackoverflow.com/q/14632828/1122270, if anyone wants a cookie. Best regards, Constantine. -- 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