Patrick Steinhardt <ps@xxxxxx> writes: > I'd prefer the latter -- always use SHA-1. As you say, it's easier to > understand and doesn't create implicit mechanisms that we'll have to > maintain going forward. Also, users didn't have a desire yet to pick a > different algorithm than SHA-1, which probably also comes from the fact > that SHA-256 repositories are still scarce. > ... > Eventually, we should then add a new option `--object-hash=` to > git-hash-object(1) and other commands that may run outside of a Git > repository to let the user pick their desired hash. If we were planning to allow using something other than SHA-1 in the future, then I do not think I agree with your argument. We can use the same GIT_DEFAULT_HASH mechanism to specify what hash to use without later adding an extra option just fine.
