Hi, Johannes Schindelin wrote: > As to the default of seriously slowing down all SHA-1 computations: since > you made that the default, at compile time, with no way to turn on the > faster computation, this will have a major, negative impact. Are you > really, really sure you want to do that? > > I thought that it was obvious that we would have at least a runtime option > to lessen the load. It's not obvious to me. I agree that the DC_SHA1 case can be sped up, e.g. by turning off the collision detection for sha1 calculations that are not part of fetching, receiving a push, or running fsck. To be clear, are you saying that this is a bad compile-time default because distributors are going to leave it and end-users will end up with a bad experience? Or are you saying distributors have no good alternative to choose at compile time? Or something else? Is there some particular downstream that this breaks? Thanks and hope that helps, Jonathan