Makefile: NO_OPENSSL=1 should no longer imply BLK_SHA1=1
commitedb6a17c36be107e87abd1ff641f317ea578e80e
authorÆvar Arnfjörð Bjarmason <avarab@gmail.com>
Thu, 28 Dec 2017 14:07:41 +0000 (28 14:07 +0000)
committerJunio C Hamano <gitster@pobox.com>
Thu, 28 Dec 2017 19:55:56 +0000 (28 11:55 -0800)
tree6c285fbca368a74fb473471d7e15a886d29f1ebe
parent29533fb16899725af9306e0c3b83da8954c0e48a
Makefile: NO_OPENSSL=1 should no longer imply BLK_SHA1=1

Use the collision detecting SHA-1 implementation by default even when
NO_OPENSSL is set.

Setting NO_OPENSSL=UnfortunatelyYes has implied BLK_SHA1=1 ever since
the former was introduced in dd53c7ab29 (Support for NO_OPENSSL,
2005-07-29).  That implication should have been removed when the
default SHA-1 implementation changed from OpenSSL to DC_SHA1 in
e6b07da278 (Makefile: make DC_SHA1 the default, 2017-03-17).  Finish
what that commit started by removing the BLK_SHA1 fallback setting so
the default DC_SHA1 implementation will be used.

Helped-by: Jonathan Nieder <jrnieder@gmail.com>
Reviewed-by: Jonathan Nieder <jrnieder@gmail.com>
Signed-off-by: Ævar Arnfjörð Bjarmason <avarab@gmail.com>
Reviewed-by: Jonathan Nieder <jrnieder@gmail.com>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
Makefile
configure.ac