diff options
Diffstat (limited to 'doc')
| -rw-r--r-- | doc/bugs/__96__git_annex_import__96___clobbers_mtime/comment_2_3563d9eeb9806f8ca1b9b340925837f5._comment | 18 |
1 files changed, 18 insertions, 0 deletions
diff --git a/doc/bugs/__96__git_annex_import__96___clobbers_mtime/comment_2_3563d9eeb9806f8ca1b9b340925837f5._comment b/doc/bugs/__96__git_annex_import__96___clobbers_mtime/comment_2_3563d9eeb9806f8ca1b9b340925837f5._comment new file mode 100644 index 000000000..842c713df --- /dev/null +++ b/doc/bugs/__96__git_annex_import__96___clobbers_mtime/comment_2_3563d9eeb9806f8ca1b9b340925837f5._comment @@ -0,0 +1,18 @@ +[[!comment format=mdwn + username="http://joeyh.name/" + ip="4.154.0.21" + subject="comment 2" + date="2013-07-30T17:40:04Z" + content=""" +git-annex makes only a best-effort attempt to preserve mtime. There are multiple cases where it cannot: + +* filesystems that do not support changing the mtime of a symlink +* special remotes +* when 2 files with the same content get stored in the annex, the mtime of one must win over the other since we only have 1 inode + +This last seems to be what has happened in the example you show. Both `foo` and `foobar` are empty. I'm not sure where the 01:19:41 time came from -- perhaps you had a third empty file that was not shown? + +I've tested `git annex import` and it preserves mtimes otherwise. + + +"""]] |