aboutsummaryrefslogtreecommitdiff
path: root/merge-recursive.c
diff options
context:
space:
mode:
authorDavid Turner <dturner@twosigma.com>2016-11-11 12:23:48 -0500
committerJunio C Hamano <gitster@pobox.com>2016-11-18 13:06:14 -0800
commitf8edeaa05d8623a9f6dad408237496c51101aad8 (patch)
treefaf475f7743ddb59bcde10bb1ba495f426153d45 /merge-recursive.c
parent296b847c0d6de63353e236cfbf94163d24155529 (diff)
downloadgit-f8edeaa05d8623a9f6dad408237496c51101aad8.tar.gz
git-f8edeaa05d8623a9f6dad408237496c51101aad8.tar.xz
upload-pack: optionally allow fetching any sha1
It seems a little silly to do a reachabilty check in the case where we trust the user to access absolutely everything in the repository. Also, it's racy in a distributed system -- perhaps one server advertises a ref, but another has since had a force-push to that ref, and perhaps the two HTTP requests end up directed to these different servers. Signed-off-by: David Turner <dturner@twosigma.com> Signed-off-by: Junio C Hamano <gitster@pobox.com>
Diffstat (limited to 'merge-recursive.c')
0 files changed, 0 insertions, 0 deletions