docs: Updated --track-renames docs

This commit is contained in:
Evan Harris 2020-08-03 16:30:48 -05:00 committed by Nick Craig-Wood
parent b03fcbcc12
commit 841edc729c

View file

@ -1328,8 +1328,10 @@ will be considered.
If the destination does not support server-side copy or move, rclone If the destination does not support server-side copy or move, rclone
will fall back to the default behaviour and log an error level message will fall back to the default behaviour and log an error level message
to the console. Note: Encrypted destinations are not supported to the console.
by `--track-renames`.
Encrypted destinations are not currently supported by `--track-renames`
if `--track-renames-strategy` includes `hash`.
Note that `--track-renames` is incompatible with `--no-traverse` and Note that `--track-renames` is incompatible with `--no-traverse` and
that it uses extra memory to keep track of all the rename candidates. that it uses extra memory to keep track of all the rename candidates.
@ -1358,6 +1360,8 @@ Using `--track-renames-strategy modtime` or `leaf` can enable
If nothing is specified, the default option is matching by `hash`es. If nothing is specified, the default option is matching by `hash`es.
Note that the `hash` strategy is not supported with encrypted destinations.
### --delete-(before,during,after) ### ### --delete-(before,during,after) ###
This option allows you to specify when files on your destination are This option allows you to specify when files on your destination are