diff options
| author |  martin <martin@web> | 2014-05-05 14:37:53 +0000 |
|---|---|---|
| committer |  admin <admin@branchable.com> | 2014-05-05 14:37:53 +0000 |
| commit | 50194215e003685001cc0285fde21e0b0dc7d6be (patch) | |
| tree | 0c7bfff11cf01dea9b4b726cd197f5acec390091 | |
| parent | da52d8099cc5e5a13b250cffe0c9807b2af56ade (diff) | |
| -rw-r--r-- | doc/forum/FAT:_Date_resolution_for_mtime_2s--__62___implications.mdwn | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/forum/FAT:_Date_resolution_for_mtime_2s--__62___implications.mdwn b/doc/forum/FAT:_Date_resolution_for_mtime_2s--__62___implications.mdwn index 0aa4d03ca..15790e5ef 100644 --- a/doc/forum/FAT:_Date_resolution_for_mtime_2s--__62___implications.mdwn +++ b/doc/forum/FAT:_Date_resolution_for_mtime_2s--__62___implications.mdwn @@ -1,6 +1,6 @@ The Date resolution for FAT is only 2 seconds for the "last modified time." This leads to the strange behaviour, that after umount and remount of an usb drive (direct mode) git-annex thinks that suddenly approx. 50% of -the files are modified. (after remount the times appears to be rounded to even values) +the files are modified. (after remount the times appears to be rounded to even values) So git-annex is not real "guilty" but it would be fine to create a "workaround" for this problem... Possible the best solution for this is to set even values for the seconds in the filesystem and in annex internal tables direct after the "git annex get". Other solution would be to treat differences up to 1s in modification time as unmodified or create an new parameter like rsync's "modify-window" for this. To do an "git annex sync" or git annex add is in my opinion not a good option, because one could add so Bad file content by accident... |