From a3761d6f890c41f2e51855e019053a63dcfd70f6 Mon Sep 17 00:00:00 2001 From: "https://www.google.com/accounts/o8/id?id=AItOawmmqnZzN5GP4w2m85_bSx7WSi0pMZvUVn8" Date: Tue, 1 Jul 2014 10:43:57 +0000 Subject: [PATCH] --- ...hen_synchronized_to_a_different_repository.mdwn | 14 ++++++++++++++ 1 file changed, 14 insertions(+) create mode 100644 doc/bugs/Mtime_of_objects_reset_when_synchronized_to_a_different_repository.mdwn diff --git a/doc/bugs/Mtime_of_objects_reset_when_synchronized_to_a_different_repository.mdwn b/doc/bugs/Mtime_of_objects_reset_when_synchronized_to_a_different_repository.mdwn new file mode 100644 index 0000000000..c6dcaaeba1 --- /dev/null +++ b/doc/bugs/Mtime_of_objects_reset_when_synchronized_to_a_different_repository.mdwn @@ -0,0 +1,14 @@ +### Please describe the problem. +Files transferred from one repository to a standard remote by the assistant do not retain the original mtime + +### What steps will reproduce the problem? +Create manually two repositories, in my case on two external drives directly connected to my box, with normal remotes pointing to each other. +Activate git annex assistant and synchronize some files from one to the other. + +### What version of git-annex are you using? On what operating system? +Git annex version 5.20140610-g5ec8bcf on Ubuntu Linux 12.04 + +### Please provide any additional information below. +I've noticed how files synchronized from one repository to another do not retain the original mtime information. +Perhaps it's intended, but in my view retaining the time of modification of the object is essential. +