diff options
| author |  martin <martin@web> | 2014-05-03 18:53:13 +0000 |
|---|---|---|
| committer |  admin <admin@branchable.com> | 2014-05-03 18:53:13 +0000 |
| commit | 5ad8bbf0ad4f088c2b0502ae94f1b9b528cb8b55 (patch) | |
| tree | 27493fa832dfb86dd15045a81cd86dd125c03216 | |
| parent | 411e592a9aa6ccfebe38ae2bc088cf85e76c7e2e (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 0b7efb567..a81d0cb47 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,5 +1,5 @@ The Date resolution for FAT is only 2 seconds for the "last modified time." -This leeds to the strange behaviour, that after umount and remount of an usb drive (direct mode) git-annex thinks that suddenly approx. 50% of +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... |