This is probably expected behavior, but when bisecting another Git issue[1], i found that after a fresh clone of the git repository using 1.4.4.2 I got the following corrupt pack file when accessing that repo with an old version of git: $ git --version git version 1.4.2 $ git log fatal: corrupted pack file .git/objects/pack/pack-d75f6a8307f8d8ce9727fe27107486839c54aef6.pack When reverting to 1.4.3 instead, a git reset triggered the corrupt pack error. Anyway, just a heads up in case it actually matters. Sean [1] The "Git" issue turned out not to be Git at all but rather the Beagle search daemon which seems to touch file stat information as it scans files in a git repo causing strange git status and diff results. - 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