]> git.ipfire.org Git - thirdparty/git.git/commit
Merge branch 'bc/submodule-force-same-hash' into next
authorJunio C Hamano <gitster@pobox.com>
Wed, 19 Nov 2025 18:58:43 +0000 (10:58 -0800)
committerJunio C Hamano <gitster@pobox.com>
Wed, 19 Nov 2025 18:58:43 +0000 (10:58 -0800)
commiteec9dca32c73fb1158bd0bb24e666729702c9f6b
tree02f1c5c29dc0592f7d3379a8f7e9e867b5506666
parent5d5f74f4f04e1ba3a6c9c496e9c532b370c20f9f
parent6fe288bfbcbbabc3d399dd71f876dccf71affff0
Merge branch 'bc/submodule-force-same-hash' into next

Adding a repository that uses a different hash function is a no-no,
but "git submodule add" did nt prevent it, which has been corrected.

* bc/submodule-force-same-hash:
  read-cache: drop submodule check from add_to_cache()
  object-file: disallow adding submodules of different hash algo
object-file.c
read-cache.c