From 714e665c92751620247bed6b7b8760991b441363 Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Thu, 10 Dec 2020 11:25:02 -0400 Subject: [PATCH] reorg --- doc/git-annex.mdwn | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/doc/git-annex.mdwn b/doc/git-annex.mdwn index f83398997e..9fba53ecb3 100644 --- a/doc/git-annex.mdwn +++ b/doc/git-annex.mdwn @@ -1405,12 +1405,6 @@ Remotes are configured using these settings in `.git/config`. When this happens, the transfer will be considered to have failed, so settings like annex.retry will control what it does next. - This is not enabled by default, because it can make git-annex use - more resources. In order to cancel stalls, git-annex has to run - transfers in separate processes (one per concurrent job). So it - may need to open more connections to a remote than usual, or - the communication with those processes may make it a bit slower. - The value specifies how much data git-annex should expect to see flowing, minimum, when it's not stalled, over a given period of time. The format is "$amount/$timeperiod". @@ -1423,6 +1417,12 @@ Remotes are configured using these settings in `.git/config`. stuck for a long time, you could use: `git config remote.usbdrive.annex-stalldetection "1MB/1m"` + This is not enabled by default, because it can make git-annex use + more resources. To be able to cancel stalls, git-annex has to run + transfers in separate processes (one per concurrent job). So it + may need to open more connections to a remote than usual, or + the communication with those processes may make it a bit slower. + * `remote..annex-checkuuid` This only affects remotes that have their url pointing to a directory on