diff options
author | martin <martin@web> | 2014-05-06 08:43:27 +0000 |
---|---|---|
committer | admin <admin@branchable.com> | 2014-05-06 08:43:27 +0000 |
commit | a345b15d40b41af16432fadd9de7a3f07301a18a (patch) | |
tree | 7652be5eb873c757fe1fbf5b2e36dfe4cf5867f7 | |
parent | 1a625a946706ca94810a874aa3834af1be13c0c1 (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 0deb3ceab..675292317 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 @@ -3,7 +3,7 @@ This leads to the strange behaviour, that after umount and remount of an usb dri the files are modified. (after remount the "seconds" appears to be rounded to even values - the inode cache before unmount had 1 second resolution) 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... +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: |