Skip to content
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

Syncing sets local file's modified+2hrs #938

Closed
cyberduck opened this issue Oct 21, 2006 · 1 comment
Closed

Syncing sets local file's modified+2hrs #938

cyberduck opened this issue Oct 21, 2006 · 1 comment

Comments

@cyberduck
Copy link
Collaborator

mwl created the issue

When syncing, Cyberduck recognizes a local file correctly as changed and uploads. The sync process advances the local file's modified date by about 2 hrs (from "now" to "future"). Remote file hast upload time as date modified. "Reloading" the sync process leads to another upload of the same, now unchanged file, because modified time is in the future and therefore more "current" than remote file.

@cyberduck
Copy link
Collaborator Author

cyberduck commented May 18, 2007

@dkocher commented

Duplicate for #12362. General support for timezones missing.

@iterate-ch iterate-ch locked as resolved and limited conversation to collaborators Nov 26, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants