diff options
| author |  martin <martin@web> | 2014-05-04 07:05:58 +0000 |
|---|---|---|
| committer |  admin <admin@branchable.com> | 2014-05-04 07:05:58 +0000 |
| commit | cd8c764eee6eccf651b6c8542a31ccaecfd756ea (patch) | |
| tree | 19f71fa4308e602b093c9fa2691be8997bc6607e /doc | |
| parent | 63f5c269ba348e3b23b869cdb7bc3d5f4380498a (diff) | |
Diffstat (limited to 'doc')
| -rw-r--r-- | doc/forum/FAT:_Date_resolution_for_mtime_2s--__62___implications.mdwn | 3 |
1 files changed, 2 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 f6fc9ce0d..0aa4d03ca 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 @@ -2,7 +2,8 @@ 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) -One 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... +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... Here's an konsole session to show this behaviour: |