aboutsummaryrefslogtreecommitdiff
path: root/refs.c
diff options
context:
space:
mode:
authorJunio C Hamano <gitster@pobox.com>2013-01-28 20:45:43 -0800
committerJunio C Hamano <gitster@pobox.com>2013-01-28 21:05:51 -0800
commit3f1da57fffdcfb48bd8b85da347f310b955245d7 (patch)
tree33e1e2f21663c1c08c4785c91cb94e042ec2fc5e /refs.c
parentcbbe50db7691cd9d7d261ebc5c5ffec55f93127d (diff)
downloadgit-3f1da57fffdcfb48bd8b85da347f310b955245d7.tar.gz
git-3f1da57fffdcfb48bd8b85da347f310b955245d7.tar.xz
upload-pack: simplify request validation
Long time ago, we used to punt on a large (read: asking for more than 256 refs) fetch request and instead sent a full pack, because we couldn't fit many refs on the command line of rev-list we run internally to enumerate the objects to be sent. To fix this, 565ebbf (upload-pack: tighten request validation., 2005-10-24), added a check to count the number of refs in the request and matched with the number of refs we advertised, and changed the invocation of rev-list to pass "--all" to it, still keeping us under the command line argument limit. However, these days we feed the list of objects requested and the list of objects the other end is known to have via standard input, so there is no longer a valid reason to special case a full clone request. Remove the code associated with "create_full_pack" to simplify the logic. Signed-off-by: Junio C Hamano <gitster@pobox.com>
Diffstat (limited to 'refs.c')
0 files changed, 0 insertions, 0 deletions