summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorGravatar https://www.google.com/accounts/o8/id?id=AItOawmmqnZzN5GP4w2m85_bSx7WSi0pMZvUVn8 <Fulvio@web>2014-07-01 15:45:55 +0000
committerGravatar admin <admin@branchable.com>2014-07-01 15:45:55 +0000
commit8bc4ece9f3d9af9468a6aaa6a0a841b43c283308 (patch)
tree36bf14f07956e97407507e15637505df2243f6a8
parentbf6e6e04973a3b21126654451486e0be47d23715 (diff)
-rw-r--r--doc/forum/Modification_time_of_files_retained_in_synchronized_remote_copies__63__.mdwn5
1 files changed, 5 insertions, 0 deletions
diff --git a/doc/forum/Modification_time_of_files_retained_in_synchronized_remote_copies__63__.mdwn b/doc/forum/Modification_time_of_files_retained_in_synchronized_remote_copies__63__.mdwn
new file mode 100644
index 000000000..3cd519a6d
--- /dev/null
+++ b/doc/forum/Modification_time_of_files_retained_in_synchronized_remote_copies__63__.mdwn
@@ -0,0 +1,5 @@
+I've noticed how, when files are synchronized/transferred from one repository (annex?) to another by the assistant, the files in the «remote» repository do no retain the modification time of the original files.
+From what I know git does not save file-specific metadata (ownership/timestamps/etc.).
+Since I've just started using git-annex, and I'd very much like for backup copies to retain the mtime of the originals, I would like to ask whether I am experiencing a malfunction or whether this is expected behaviour.
+
+Regards