diff options
| author | David Pursehouse <david.pursehouse@sonymobile.com> | 2015-10-22 12:32:56 +0900 |
|---|---|---|
| committer | David Pursehouse <david.pursehouse@sonymobile.com> | 2015-10-22 13:35:06 +0900 |
| commit | 10b903e488519a215dc0701c9e275745fbca5b9a (patch) | |
| tree | b2c1b2bc10a54223781143351c1594dd91417a88 | |
| parent | af5edf6047f2a730c5a9fbc6b08dad6edba21dab (diff) | |
Remove obsolete remote.NAME.timeout from config documentation
This configuration setting is no longer used. Remove it from the
documentation.
Change-Id: Id3a9896997e150e37c54e872a650bb8b16c112f6
| -rw-r--r-- | src/main/resources/Documentation/config.md | 13 |
1 files changed, 0 insertions, 13 deletions
diff --git a/src/main/resources/Documentation/config.md b/src/main/resources/Documentation/config.md index bea2d92..29626d8 100644 --- a/src/main/resources/Documentation/config.md +++ b/src/main/resources/Documentation/config.md @@ -182,19 +182,6 @@ remote.NAME.push [2]: #example_file -remote.NAME.timeout -: Number of seconds to wait for a network read or write to - complete before giving up and declaring the remote side is not - responding. If 0, there is no timeout, and the push client - waits indefinitely. - - A timeout should be large enough to mostly transfer the - objects to the other side. 1 second may be too small for - larger projects, especially over a WAN link, while 10-30 - seconds is a much more reasonable timeout value. - - Defaults to 0 seconds, wait indefinitely. - remote.NAME.replicationDelay : Number of seconds to wait before scheduling a remote push operation. Setting the delay to 0 effectively disables the |