summaryrefslogtreecommitdiff
path: root/t/t9136
diff options
context:
space:
mode:
authorLibravatar brian m. carlson <sandals@crustytoothpaste.net>2020-05-25 19:59:05 +0000
committerLibravatar Junio C Hamano <gitster@pobox.com>2020-05-27 10:07:06 -0700
commitb65dc2cebd6ac7d869895297ed5061af15428544 (patch)
treec20a67ad36062c7e5dd6ac71b6cfd442894ebf48 /t/t9136
parentremote-curl: implement object-format extensions (diff)
downloadtgif-b65dc2cebd6ac7d869895297ed5061af15428544.tar.xz
builtin/clone: initialize hash algorithm properly
When performing a clone, we don't know what hash algorithm the other end will support. Currently, we don't support fetching data belonging to a different algorithm, so we must know what algorithm the remote side is using in order to properly initialize the repository. We can know that only after fetching the refs, so if the remote side has any references, use that information to reinitialize the repository with the correct hash algorithm information. Signed-off-by: brian m. carlson <sandals@crustytoothpaste.net> Signed-off-by: Junio C Hamano <gitster@pobox.com>
Diffstat (limited to 't/t9136')
0 files changed, 0 insertions, 0 deletions