Revert "Remove obsolete remote.NAME.timeout from config documentation"

Although the timeout setting is not explicitly read in the plugin's
implementation, it is actually used by JGit when pushing to the remote:

  tn.applyConfig(config);

so it was wrong to remove this documentation.  Add it back.

This reverts commit 10b903e488519a215dc0701c9e275745fbca5b9a.

Change-Id: I50892e73136b369ec5822b9d7039ad918e2f6d05

src/main/resources/Documentation/config.md

diff --git a/src/main/resources/Documentation/config.md b/src/main/resources/Documentation/config.md
index 54251ce..a528565 100644
--- a/src/main/resources/Documentation/config.md
+++ b/src/main/resources/Documentation/config.md
@@ -182,6 +182,19 @@
 
 [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
 :	Time to wait before scheduling a remote push operation. Setting
 	the delay to 0 effectively disables the delay, causing the push