diff options
| -rw-r--r-- | doc/bugs/Windows_file_timestamp_timezone_madness/comment_3_7fe149bedb8ceab75953996ac8e20f0f._comment | 20 |
1 files changed, 20 insertions, 0 deletions
diff --git a/doc/bugs/Windows_file_timestamp_timezone_madness/comment_3_7fe149bedb8ceab75953996ac8e20f0f._comment b/doc/bugs/Windows_file_timestamp_timezone_madness/comment_3_7fe149bedb8ceab75953996ac8e20f0f._comment new file mode 100644 index 000000000..1a25d3c82 --- /dev/null +++ b/doc/bugs/Windows_file_timestamp_timezone_madness/comment_3_7fe149bedb8ceab75953996ac8e20f0f._comment @@ -0,0 +1,20 @@ +[[!comment format=mdwn + username="http://joeyh.name/" + ip="108.236.230.124" + subject="comment 3" + date="2014-06-11T22:11:38Z" + content=""" +I have implemented this on the loststamp git branch. It seems to work! + +However, it has a big problem: + + If the timezone changes while the assistant (or a long-running command) + runs, it won't notice, since it only checks the inode cache once, and + so will use the old delta for all new inode caches it generates for new + files it's added. Which will result in them seeming changed the next time + it runs. + +So, it would be really nice to be able to check the actual timezone instead. +But I suppose I can make the assistant poll the inode cache file, or check +it when adding a new file, or something like that. Bleagh. +"""]] |