On Fri, Mar 26, 2010 at 7:50 PM, Junio C Hamano <gitster@xxxxxxxxx> wrote: > "Shawn O. Pearce" <spearce@xxxxxxxxxxx> writes: > >> Scott, please fix that library on GitHub. JGit's fsck has a hard >> failure on these malformed trees, because the leading '0' mode >> causes the tree to come up with the wrong SHA-1 hash given its >> logical content. They shouldn't be created like this. > > What is curious is that even though 6407180 (git-fsck-cache: be stricter > about "tree" objects, 2005-07-27) does talk about zero-padding, it appears > that we never had a version of git that padded mode in '0' in the entire > history of write-tree (except that "notes tree" one, but even that didn't > escape the laboratory). It's apparently an easy mistake to make. bup did this for a while until I added a 'git fsck' to its automated tests :) The problem is that everything in git works perfectly with these invalid file modes *except* fsck, and there's rarely a need to run fsck, so this problem can hide for a long time. Have fun, Avery -- 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