Hi! Eric S. Raymond wrote: > One reason I am sure of this is the SHA-1 to whatever transition. > We can't count on the successor hash to survive attack forever. > Accordingly, git's design needs to be stable against the possibility > of having to accommodate multiple future hash algorithms in the > future. Have you read through Documentation/technical/hash-function-transition? It takes the case where the new hash function is found to be weak into account. Hope that helps, Jonathan
