-
Notifications
You must be signed in to change notification settings - Fork 506
Push of directory changes file modification times #50
Comments
Yes, I would assume that it wouldn't even do a push since the files are the same. If I do a push on a directory and then do the same command again without changing any files, I would expect the push command to say 'up to date'. But it does another full push again. |
My main issue with this that the program should not appear to modify the files it uploads. |
But then how will the last edit time match up between your local files and those on the cloud? Why is this an issue? See everytime a push is made, the mod time for the file remotely is changed. The change is just to keep times in sync. |
It is an issue bevause the mod time for the file should only change if the file has been modified. The copy on the cloud should have the local mod time if it has just been pushed. |
yes I agree with @neilromig. The modified time should match what is on the source with a push and same with a pull from google. |
I agree also. It would be nice if drive did not change modification times. If it is necessary to keep the modification times in sync then it should send the modification time along with the file. By the way, thank you @odeke-em for keeping this project alive! |
Please checkout the latest from my fork since the project moved there, and then reopen the issue there if it persists. @mattlbaker glad you are able to use drive. |
I am pushing a directory to my Google Drive account and files in uploaded directories and subdirectories all have their times (modification, access and change) set to the time drive has uploaded them. Those not uploaded remain unaltered.
The text was updated successfully, but these errors were encountered: