From 21da74870662839da591e652b477352030fc0528 Mon Sep 17 00:00:00 2001 From: "https://www.google.com/accounts/o8/id?id=AItOawlM_DRhi_5pJrTA0HbApHR25iAgy-NBXTY" Date: Wed, 1 Oct 2014 22:02:56 +0000 Subject: [PATCH] Added a comment --- .../comment_6_52842fb7828267894ce59528e7b28b31._comment | 9 +++++++++ 1 file changed, 9 insertions(+) create mode 100644 doc/bugs/sync_does_not_preserve_timestamps/comment_6_52842fb7828267894ce59528e7b28b31._comment diff --git a/doc/bugs/sync_does_not_preserve_timestamps/comment_6_52842fb7828267894ce59528e7b28b31._comment b/doc/bugs/sync_does_not_preserve_timestamps/comment_6_52842fb7828267894ce59528e7b28b31._comment new file mode 100644 index 0000000000..dabc403299 --- /dev/null +++ b/doc/bugs/sync_does_not_preserve_timestamps/comment_6_52842fb7828267894ce59528e7b28b31._comment @@ -0,0 +1,9 @@ +[[!comment format=mdwn + username="https://www.google.com/accounts/o8/id?id=AItOawlM_DRhi_5pJrTA0HbApHR25iAgy-NBXTY" + nickname="Tor Arne" + subject="comment 6" + date="2014-10-01T22:02:56Z" + content=""" +I was just about to start using git-annex for my data when I saw this bug report, which unfortunately is a blocker. Persisting basic metadata of files that are synced seems like a core feature of a file sync/transfer tool, so I'm really hoping this can be solved somehow :/ + +"""]]