diff options
| author |  Joey Hess <joey@kitenet.net> | 2014-06-11 14:32:01 -0400 |
|---|---|---|
| committer | Joey Hess <joey@kitenet.net> | 2014-06-11 14:32:01 -0400 |
| commit | 7809713fb2b000c0eac61e373f2a09b0a2b0257a (patch) | |
| tree | 3bc2714f68e78cb3b1f997edc6eabcb0831ba710 | |
| parent | bac59cece66e97900554fdee394e8f86027a7d25 (diff) | |
split out bug report from FAT:_Date_resolution_for_mtime_2s--__62___implications
| -rw-r--r-- | doc/bugs/Windows_file_timestamp_timezone_madness.mdwn | 16 |
1 files changed, 16 insertions, 0 deletions
diff --git a/doc/bugs/Windows_file_timestamp_timezone_madness.mdwn b/doc/bugs/Windows_file_timestamp_timezone_madness.mdwn new file mode 100644 index 000000000..a90c58f24 --- /dev/null +++ b/doc/bugs/Windows_file_timestamp_timezone_madness.mdwn @@ -0,0 +1,16 @@ +Windows has an unfortunate handling of time zones, which means that when +the time zone is changed (or DST changes), the timestamps of files also +appear to change. + +This means that after such a change, git-annex will see new mtimes, and +want to re-checksum every file in the repo. + +The best way to fix this seems to be to normalize the timestamp returned by +getFileStatus, which is relative to the current time zone, to be relative +to UTC. (As is always the case on Unix, of course). +However, to do that, I need to know the current timezone. + +Unfortunately, Data.Time.LocalTime.getCurrentTimeZone doesn't seem to really +work on windows. It always returns a time zone 60 minutes from UTS in my tests, +no matter what the zone really is. I need to test this more widely and file +a GHC bug if appropriate. |