Skip to content
This repository has been archived by the owner on Sep 3, 2020. It is now read-only.

Push of directory changes file modification times #50

Open
neilromig opened this issue Dec 24, 2014 · 7 comments
Open

Push of directory changes file modification times #50

neilromig opened this issue Dec 24, 2014 · 7 comments

Comments

@neilromig
Copy link

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.

@ikwyl6
Copy link

ikwyl6 commented Dec 28, 2014

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.

@neilromig
Copy link
Author

My main issue with this that the program should not appear to modify the files it uploads.

@odeke-em
Copy link
Contributor

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.

@neilromig
Copy link
Author

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.

@ikwyl6
Copy link

ikwyl6 commented Dec 31, 2014

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.

@codecentaur
Copy link

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!

@odeke-em
Copy link
Contributor

odeke-em commented Jan 4, 2015

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.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants