Fatal: <hash> is corrupted can be caused by wrong permissions

A quick search of your mailing list didn't turn up any good hits (not the most searchable terms and gmane search doesn't seem to support phrases), so I'm reporting this.

On git 1.7.1 I ran into the Fatal corruption error in one of my projects. For reasons that are irrelevant I was operating on the repo as user X, a member of group Z, but the files were all owned by Y:Z, with (I thought) -rw-rw--- permissions. After a bunch of head banging I finally figured out that the Fatal error wasn't because the object files were corrupted, but because three objects (for reasons unknown to me that are probably lost in the early history of the setup of this particular repo...one of the blobs was the first commit) were -rw-----. So it seems to me that the error message could be improved to indicate that the reason the object couldn't be used was a permission error. That's a different thing from the contents being corrupted.

--David