-
Notifications
You must be signed in to change notification settings - Fork 4
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
Provide detection mode for parameter epoch_delta #12
Comments
https://github.com/marcus67/gitsynchista/blob/master/doc/tutorial.md#correcting-a-time-shift Is this caused because you live in Germany and our timezone is one hour shifted from UTC / GMT? Would this epoch_delta need to be modified for those who live in other timezones? |
It may be linked to the time-zone. I will have to write to the developer of Working Copy to find out which time he uses when returning the time stamps of the WebDav server. |
I made some quick tests with curl and the dates the WebDav server responds with are always GMT, but it also correctly specifies this as part of the field. It can be something like
This for a file I edited a few minutes ago. I also reside in the German timezone such that edits where made 8:51. It should be possible to parse the date such that timezone is taken into account. Depending on how Python handles dates, the fix could also be something that is done when reading dates from the filesystem, such that you somehow attach your local timezone to the dates. I made some tests connecting to the WebDAV server with Transmit on my Mac and it shows correct timestamps for files, in my local timezone. |
I will look into this again. I think I use a Python function which scans the time zone info but I haven't manually checked the epoch value yet. Thanks for checking! |
No description provided.
The text was updated successfully, but these errors were encountered: