summaryrefslogtreecommitdiff
path: root/t/t7500/add-content
diff options
context:
space:
mode:
authorLibravatar Jonathan Tan <jonathantanmy@google.com>2022-01-24 10:09:09 -0800
committerLibravatar Junio C Hamano <gitster@pobox.com>2022-01-26 11:12:19 -0800
commitdccea605b6c30262a6a44bde8d10b0a20c331d87 (patch)
treeb1c222ce5c208fa720fa08c7d28b88adacdb918e /t/t7500/add-content
parentGit 2.34.1 (diff)
downloadtgif-dccea605b6c30262a6a44bde8d10b0a20c331d87.tar.xz
clone: support unusual remote ref configurations
When cloning a branchless and tagless but not refless remote using protocol v0 or v1, Git calls transport_fetch_refs() with an empty ref list. This makes the clone fail with the message "remote transport reported error". Git should have refrained from calling transport_fetch_refs(), just like it does in the case that the remote is refless. Therefore, teach Git to do this. In protocol v2, this does not happen because the client passes ref-prefix arguments that filter out non-branches and non-tags in the ref advertisement, making the remote appear empty. Note that this bug concerns logic in builtin/clone.c and only affects cloning, not fetching. Signed-off-by: Jonathan Tan <jonathantanmy@google.com> Signed-off-by: Junio C Hamano <gitster@pobox.com>
Diffstat (limited to 't/t7500/add-content')
0 files changed, 0 insertions, 0 deletions