document get -J's behavior of spreading load amoung same-cost remotes
I implemented this last fall, but forgot to document it anywhere.
This commit is contained in:
parent
384027bc79
commit
fde5dbff2b
1 changed files with 8 additions and 1 deletions
|
@ -23,7 +23,7 @@ or transferring them from some kind of key-value store.
|
||||||
* `--from=remote`
|
* `--from=remote`
|
||||||
|
|
||||||
Normally git-annex will choose which remotes to get the content
|
Normally git-annex will choose which remotes to get the content
|
||||||
from, preferring less expensive remotes. Use this option to specify
|
from, preferring remotes with lower costs. Use this option to specify
|
||||||
which remote to use.
|
which remote to use.
|
||||||
|
|
||||||
Any files that are not available on the remote will be silently skipped.
|
Any files that are not available on the remote will be silently skipped.
|
||||||
|
@ -33,6 +33,13 @@ or transferring them from some kind of key-value store.
|
||||||
Enables parallel download with up to the specified number of jobs
|
Enables parallel download with up to the specified number of jobs
|
||||||
running at once. For example: `-J10`
|
running at once. For example: `-J10`
|
||||||
|
|
||||||
|
When files can be downloaded from multiple remotes, enabling parallel
|
||||||
|
downloads will split the load between the remotes. For example, if
|
||||||
|
the files are available on remotes A and B, then one file will be
|
||||||
|
downloaded from A, and another file will be downloaded from B in
|
||||||
|
parallel. (Remotes with lower costs are still preferred over higher cost
|
||||||
|
remotes.)
|
||||||
|
|
||||||
* file matching options
|
* file matching options
|
||||||
|
|
||||||
The [[git-annex-matching-options]](1)
|
The [[git-annex-matching-options]](1)
|
||||||
|
|
Loading…
Add table
Add a link
Reference in a new issue