aboutsummaryrefslogtreecommitdiff
path: root/pack-revindex.h
diff options
context:
space:
mode:
authorShawn O. Pearce <spearce@spearce.org>2011-03-14 16:48:39 -0700
committerJunio C Hamano <gitster@pobox.com>2011-03-14 17:27:25 -0700
commit49bee717f7080f99d3405682cc43ad525dde0973 (patch)
treecb193a31ca95a8f31f1e7f70dd8f07d02eda09c3 /pack-revindex.h
parent7ed863a85a6ce2c4ac4476848310b8f917ab41f9 (diff)
downloadgit-49bee717f7080f99d3405682cc43ad525dde0973.tar.gz
git-49bee717f7080f99d3405682cc43ad525dde0973.tar.xz
upload-pack: More aggressively send 'ACK %s ready'
If a client is merely following the remote (and has not made any new commits itself), all "have %s" lines sent by the client will be common to the server. As all lines are common upload-pack never calls ok_to_give_up() and does not compute if it has a good cut point in the commit graph. Without this computation the following client is going to send all tagged commits, as these were determined to be COMMON_REF during the initial advertisement, but the client does not parse their history to transitively pass the COMMON flag and empty its queue of commits. For git.git with 339 commit tags, it takes clients 11 rounds of negotation to fully send all tagged commits and exhaust its queue of things to send as common. This is pretty slow for a client that has not done any local development activity. Force computing ok_to_give_up() and send "ACK %s ready" at the end of the current round if this round only contained common objects and ok_to_give_up() was therefore not called. This may allow the client to break early, avoiding transmission of the COMMON_REFs. Signed-off-by: Shawn O. Pearce <spearce@spearce.org> Signed-off-by: Junio C Hamano <gitster@pobox.com>
Diffstat (limited to 'pack-revindex.h')
0 files changed, 0 insertions, 0 deletions