TrueCloudLab/rclone
16
0
Fork 2
Code Issues 1 Pull requests 1 Projects Releases Packages Wiki Activity Actions

Clarify logging and docs for --no-traverse incompatibilities - fixes #1059

Browse source
This commit is contained in:
Nick Craig-Wood 2017-02-08 22:35:12 +00:00
parent d091d4a8bb
commit c0ad29c06c
2 changed files with 4 additions and 2 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

2
docs/content/docs.md
View file

@ -722,6 +722,8 @@ This option defaults to `false`.
The `--no-traverse` flag controls whether the destination file system
is traversed when using the `copy` or `move` commands.
`--no-traverse` is not compatible with `sync` and will be ignored if
you supply it with `sync`.
If you are only copying a small number of files and/or have a large
number of files on the destination then `--no-traverse` will stop

4
fs/sync.go
View file

@ -72,7 +72,7 @@ func newSyncCopyMove(fdst, fsrc Fs, deleteMode DeleteMode, DoMove bool) (*syncCo
trackRenamesCh: make(chan Object, Config.Checkers),
}
if s.noTraverse && s.deleteMode != DeleteModeOff {
Debug(s.fdst, "Ignoring --no-traverse with sync")
ErrorLog(nil, "Ignoring --no-traverse with sync")
s.noTraverse = false
}
if s.trackRenames {
@ -92,7 +92,7 @@ func newSyncCopyMove(fdst, fsrc Fs, deleteMode DeleteMode, DoMove bool) (*syncCo
s.deleteMode = DeleteModeAfter
}
if s.noTraverse {
Debug(s.fdst, "Ignoring --no-traverse with --track-renames")
ErrorLog(nil, "Ignoring --no-traverse with --track-renames")
s.noTraverse = false
}
}