summaryrefslogtreecommitdiff
path: root/utf8.c
diff options
context:
space:
mode:
authorJonathan Tan <jonathantanmy@google.com>2019-11-13 00:34:20 (GMT)
committerJunio C Hamano <gitster@pobox.com>2019-11-13 02:50:58 (GMT)
commit603960b50edeb1f0afa694f2f0283e553c031129 (patch)
tree22ad03c602452032557113d7a0d9622d2a54e9d2 /utf8.c
parente362fadcd03753471cf8e7fc91d6d721b7423b8f (diff)
downloadgit-603960b50edeb1f0afa694f2f0283e553c031129.zip
git-603960b50edeb1f0afa694f2f0283e553c031129.tar.gz
git-603960b50edeb1f0afa694f2f0283e553c031129.tar.bz2
promisor-remote: remove fetch_if_missing=0
Commit 6462d5eb9a ("fetch: remove fetch_if_missing=0", 2019-11-08) strove to remove the need for fetch_if_missing=0 from the fetching mechanism, so it is plausible to attempt removing fetch_if_missing=0 from the lazy-fetching mechanism in promisor-remote as well. But doing so reveals a bug - when the server does not send an object pointed to by a tag object, an infinite loop occurs: Git attempts to fetch the missing object, which causes a deferencing of all refs (for negotiation), which causes a lazy fetch of that missing object, and so on. This bug is because of unnecessary use of the fetch negotiator during lazy fetching - it is not used after initialization, but it is still initialized (which causes the dereferencing of all refs). Thus, when the negotiator is not used during fetching, refrain from initializing it. Then, remove fetch_if_missing from promisor-remote. Signed-off-by: Jonathan Tan <jonathantanmy@google.com> Signed-off-by: Junio C Hamano <gitster@pobox.com>
Diffstat (limited to 'utf8.c')
0 files changed, 0 insertions, 0 deletions