Added a comment
authorhttps://me.yahoo.com/a/EbvxpTI_xP9Aod7Mg4cwGhgjrCrdM5s-#7c0f4 <https://me.yahoo.com/a/EbvxpTI_xP9Aod7Mg4cwGhgjrCrdM5s-#7c0f4@web>
Mon, 21 Dec 2015 15:46:53 +0000 (15:46 +0000)
committeradmin <admin@branchable.com>
Mon, 21 Dec 2015 15:46:53 +0000 (15:46 +0000)
doc/bugs/Mtime_of_objects_reset_when_synchronized_to_a_different_repository/comment_2_1b17514fb769fa5668f1b77e09ff3de1._comment [new file with mode: 0644]

diff --git a/doc/bugs/Mtime_of_objects_reset_when_synchronized_to_a_different_repository/comment_2_1b17514fb769fa5668f1b77e09ff3de1._comment b/doc/bugs/Mtime_of_objects_reset_when_synchronized_to_a_different_repository/comment_2_1b17514fb769fa5668f1b77e09ff3de1._comment
new file mode 100644 (file)
index 0000000..b70082b
--- /dev/null
@@ -0,0 +1,7 @@
+[[!comment format=mdwn
+ username="https://me.yahoo.com/a/EbvxpTI_xP9Aod7Mg4cwGhgjrCrdM5s-#7c0f4"
+ subject="comment 2"
+ date="2015-12-21T15:46:53Z"
+ content="""
+FWIW well -- git-annex does at least a bit to maintain mtime.  E.g. when I 'annex add' a file, the symlink's mtime becomes the one of the original file.  Unfortunately it is not the case though whenever I acquire the load for that key, which possibly gets correct mtime again, but then symlink doesn't get mtime adjusted to match to the one of the key.
+"""]]