-
Notifications
You must be signed in to change notification settings - Fork 39
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
--dry-run doesn't record actions #17
Comments
Thanks @erakli, |
Got it. You can close it.
… On 13 Jan 2019, at 18:20, Chris ***@***.***> wrote:
Thanks @erakli,
The messaging is inconsistent because the transfer to Path1 is done with individual rclone copy and delete commands for every different file on Path2, while the final transaction to make Path2 look like Path1 is done with a single rlcone sync command.
See issue #8 for more insight on the process flow. (Note that the new proposed process flow has not been implemented yet - it is not in V2.2 and newer. I'll update the issue to clarify.) Since the current final operation is an rclone sync the messages will remain inconsistent.
Also, check out the --dry-run oddity note in the README.md.
I propose to close this issue, agreed?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.
|
If we try to do
--first-run
and--dry-run
in case when there are new files in cloud (for instance), we'll get proper try to copy new files in localBut then, we get messages like the next one (notice, that paths are same, despite they are in Russian)
There should be some sort of recording, because it looks inconsistent.
The text was updated successfully, but these errors were encountered: