summaryrefslogtreecommitdiffstats
path: root/object-store-ll.h
diff options
context:
space:
mode:
authorEric W. Biederman <ebiederm@xmission.com>2023-10-02 04:40:08 +0200
committerJunio C Hamano <gitster@pobox.com>2023-10-02 23:57:38 +0200
commit15a1ca1abe8dafa9bf3bf924b4e3c6b851717ee2 (patch)
tree439500b04931250d3fa470e2c613a92f6b4f8627 /object-store-ll.h
parentobject-names: support input of oids in any supported hash (diff)
downloadgit-15a1ca1abe8dafa9bf3bf924b4e3c6b851717ee2.tar.xz
git-15a1ca1abe8dafa9bf3bf924b4e3c6b851717ee2.zip
repository: add a compatibility hash algorithm
We currently have support for using a full stage 4 SHA-256 implementation. However, we'd like to support interoperability with SHA-1 repositories as well. The transition plan anticipates a compatibility hash algorithm configuration option that we can use to implement support for this. Let's add an element to the repository structure that indicates the compatibility hash algorithm so we can use it when we need to consider interoperability between algorithms. Add a helper function repo_set_compat_hash_algo that takes a compatibility hash algorithm and sets "repo->compat_hash_algo". If GIT_HASH_UNKNOWN is passed as the compatibility hash algorithm "repo->compat_hash_algo" is set to NULL. For now, the code results in "repo->compat_hash_algo" always being set to NULL, but that will change once a configuration option is added. Inspired-by: brian m. carlson <sandals@crustytoothpaste.net> Signed-off-by: Eric W. Biederman <ebiederm@xmission.com> Signed-off-by: Junio C Hamano <gitster@pobox.com>
Diffstat (limited to 'object-store-ll.h')
0 files changed, 0 insertions, 0 deletions