gsync
gsync copied to clipboard
Preserve modification times
Maybe I'm somehow missing something... I cannot seem to adequately preserve the modification times when transferring files over to my google drive. Due to this, the -u option does not have any effect when transferring back to the local drive. I've tried the -t option, but in some cases it does not preserve the times in google drive. I assume this feature has not been implemented.
I have recently been implementing regression to test and verify features of gsync against those of rsync. This was something that came up when not using the --archive or -a option. I am in the process of fixing defects on head, but it is somewhat broken at the moment given the overhaul for pylint compliance. I will be putting some more hours in soon, but until then, can you try --archive and see if this works?
On 18 March 2014 17:57, mullenkamp [email protected] wrote:
Maybe I'm somehow missing something... I cannot seem to adequately preserve the modification times when transferring files over to my google drive. Due to this, the -u option does not have any effect when transferring back to the local drive. I've tried the -t option, but in some cases it does not preserve the times in google drive. I assume this feature has not been implemented.
Reply to this email directly or view it on GitHubhttps://github.com/iwonbigbro/gsync/issues/44 .
Oh ok, so I didn't mess up something then. I tried the archive option originally, but since the -D option has not been implemented in gsync the archive option simply fails outright. Because of that, I simply used all of the other archive options with gsync (including -t) with -u and this is the final result (as I described to you earlier). Without adding in the -t option, the mod times are not preserved and the -u option is not effective.
Nevertheless, I am very grateful that you are working on this and I have no doubt that you will have this functioning just like rsync at some point. Thanks again.
Now that #head is stable again, I will be setting up regression tests. Most of which will be centred on ensuring behaviour of rsync and gsync is as identical as it can be.
Fantastic! Thank you very much for your efforts. I'm really looking forward to actively using gsync.