On Tue, 27 Jan 2009, PJ Hyett wrote: > > ~/Development/github(jetty)$ git fsck --full > warning in tree 0d640d99b492b0c7db034e92d0460a7f84b22356: contains zero-padded file modes > .. Ouch. This is unrelated to your issue, but I'm wondering what project contains these invalid trees, and how they were created. Zero-padded tree entries can cause "object aliases", ie two trees that have logically the same contents end up with different data (due to different amounts of padding) and thus different SHA1's. It shouldn't be serious per se, but it's somethign that really shouldn't happen. What project does it come from, and how did such a tree get generated? Linus -- 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
