summaryrefslogtreecommitdiff
path: root/Documentation/config.txt
diff options
context:
space:
mode:
authorLibravatar Junio C Hamano <gitster@pobox.com>2013-09-20 12:39:05 -0700
committerLibravatar Junio C Hamano <gitster@pobox.com>2013-09-20 12:39:05 -0700
commit7b8315bb593c38ac957486916512e9a5df6df087 (patch)
tree626821ff6571b15d40f08fb13a6efb3c9f362c18 /Documentation/config.txt
parentMerge branch 'fc/at-head' (diff)
parentupload-pack: bump keepalive default to 5 seconds (diff)
downloadtgif-7b8315bb593c38ac957486916512e9a5df6df087.tar.xz
Merge branch 'jk/upload-pack-keepalive'
When running "fetch -q", a long silence while the sender side computes the set of objects to send can be mistaken by proxies as dropped connection. The server side has been taught to send a small empty messages to keep the connection alive. * jk/upload-pack-keepalive: upload-pack: bump keepalive default to 5 seconds upload-pack: send keepalive packets during pack computation
Diffstat (limited to 'Documentation/config.txt')
-rw-r--r--Documentation/config.txt11
1 files changed, 11 insertions, 0 deletions
diff --git a/Documentation/config.txt b/Documentation/config.txt
index b320b63b91..c3f70023ec 100644
--- a/Documentation/config.txt
+++ b/Documentation/config.txt
@@ -2288,6 +2288,17 @@ uploadpack.allowtipsha1inwant::
of a hidden ref (by default, such a request is rejected).
see also `uploadpack.hiderefs`.
+uploadpack.keepalive::
+ When `upload-pack` has started `pack-objects`, there may be a
+ quiet period while `pack-objects` prepares the pack. Normally
+ it would output progress information, but if `--quiet` was used
+ for the fetch, `pack-objects` will output nothing at all until
+ the pack data begins. Some clients and networks may consider
+ the server to be hung and give up. Setting this option instructs
+ `upload-pack` to send an empty keepalive packet every
+ `uploadpack.keepalive` seconds. Setting this option to 0
+ disables keepalive packets entirely. The default is 5 seconds.
+
url.<base>.insteadOf::
Any URL that starts with this value will be rewritten to
start, instead, with <base>. In cases where some site serves a