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

Local file timestamp changed during file compare #7789

Closed
cyberduck opened this issue Feb 12, 2014 · 3 comments
Closed

Local file timestamp changed during file compare #7789

cyberduck opened this issue Feb 12, 2014 · 3 comments

Comments

@cyberduck
Copy link
Collaborator

@cyberduck cyberduck commented Feb 12, 2014

71d7f84 created the issue

When I drag a file from a remote server whose files are listed in Cyberduck to a Finder window containing a file of the same name, Cyberduck opens up a window asking me if I want to overwrite the file and showing a comparison of the two files (sizes and time stamps). However, the time stamp shown for the local file is always the current time (i.e. the time from the system clock at the moment the comparison was initiated). It turns out that Cyberduck changes the time stamp of the local file at that very moment. (If I check the time stamp in a terminal using ls -l while the Cyberduck comparison/overwrite dialog window is up, it is the same as in the time stamp for the local file shown by Cyberduck.)

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Feb 12, 2014

@dkocher commented

Added test in 19ef661,

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Feb 12, 2014

@dkocher commented

This only affects downloads initiated with drag and drop to Finder.app.

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Feb 12, 2014

@dkocher commented

In 770947e.

@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