Linus Torvalds <torvalds@xxxxxxxx> writes: > That said, the pack-file should all be written with the "sha1write()" > interface, which is very careful indeed. > > I wonder if the _pack-file_ itself might be ok, and the problem is an > index file corruption. For some reason we check the index file first, > which is insane. We should check that the pack-file matches its _own_ SHA1 > first, and check the index file second. We need to check both, so I fail to see why the order matters. > If it's just the index file that is corrupt, you may even have a chance to > recover the data. > > The index file is also written with sha1write(), though, so I really don't > see where it would break. Unless you just simply literally have data > corruption on the server for some strange reason. I haven't seen this, and was wondering why. Independently, and probably unrelated, but another person reported failure while cloning, but the log appeared it had trouble spawning the git-index-pack executable for some reason. - : 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