Linus Torvalds <torvalds@xxxxxxxx> writes: > Anyway, the way to do it (if you want to use git to document SHA1 hash > mismatches) is to just check the files that have an identical SHA1 in. It > will magically work! > > Why? Because a git SHA1 is actually _not_ the SHA1 of the file itself, > it's the SHA1 of the file _with_the_git_header_added_. > > So if you find two files that have the same SHA1, they would also have to > have the same length in order to actually generate the same object name. Well, conflicting files will most probably have the same size, like with MD5 cases :-) -- Krzysztof Halasa - 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