Re: Why SHA are 40 bytes? (aka looking for flames)

On Saturday 2007, April 21, Marco Costalba wrote:

Well apart from being easier than working out the optimum size for every single object write, one really good reason would be that there is no way to predict that an object in the future won't have a conflicting SHA - every object /has/ to be stored with its full hash, because you are preventing conflicts with everything object now, in the past and all possible futures.

Wow - git is like a time machine.

Andy