move to todo

7 files changed, 0 insertions, 75 deletions

diff --git a/doc/bugs/sync_does_not_preserve_timestamps.mdwn b/doc/bugs/sync_does_not_preserve_timestamps.mdwn
deleted file mode 100644
index 0d8f2371d..000000000
--- a/doc/bugs/sync_does_not_preserve_timestamps.mdwn
+++ /dev/null
@@ -1,16 +0,0 @@
-### Please describe the problem.
-I see that files are synced between my computers with git-annex but the timestamps do not match. The one that receives files always puts the current time of file creation on the file.
-
-### What steps will reproduce the problem?
-Install git-annex on two computers. Connect with XMPP. Then add cloud storage with shared encryption for transferring files. Since you want also backup, choose "full backup" as the type of cloud storage.
-
-
-### What version of git-annex are you using? On what operating system?
-Downloaded binary package dated 13/09/2014 amd64 Ubuntu 14.04.
-
-
-### Please provide any additional information below.
-
-Files are in sync. For example, I move a file from a directory to my synced annex directory. It contains timestamp of 01/01/2010 for example. Once the file gets transferred to the remote computer, it gets current time, for example 20/09/2014 rather than keeping 01/01/2010. 
-
-All computers are linux based, ext4 filesystems. File transfers are done through shared encryption rsync remote.
diff --git a/doc/bugs/sync_does_not_preserve_timestamps/comment_1_caf5e5cb17f4d05fff8c2fab661cd93f._comment b/doc/bugs/sync_does_not_preserve_timestamps/comment_1_caf5e5cb17f4d05fff8c2fab661cd93f._comment
deleted file mode 100644
index 48ec44d2b..000000000
--- a/doc/bugs/sync_does_not_preserve_timestamps/comment_1_caf5e5cb17f4d05fff8c2fab661cd93f._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- ip="209.250.56.144"
- subject="comment 1"
- date="2014-09-23T20:27:25Z"
- content="""
-The closest git comes to storing a timestamp is the date of the last commit of a file for mtime, and first commit for ctime. However, those are pretty expensive to look up for a given file. And git doesn't try to preserve timestamps in checkouts at all, which argues that git-annex, at least at the command line, should not either.
-"""]]
diff --git a/doc/bugs/sync_does_not_preserve_timestamps/comment_2_c337fca1474b5b78f61ad6f421138ae4._comment b/doc/bugs/sync_does_not_preserve_timestamps/comment_2_c337fca1474b5b78f61ad6f421138ae4._comment
deleted file mode 100644
index 4b5a750cf..000000000
--- a/doc/bugs/sync_does_not_preserve_timestamps/comment_2_c337fca1474b5b78f61ad6f421138ae4._comment
+++ /dev/null
@@ -1,12 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawmK0703vNSIQsP1mGf-4MAPnsBZiSc6yVo"
- nickname="Emre"
- subject="comment 2"
- date="2014-09-23T20:58:10Z"
- content="""
-Thanks Joey for the comment. 
-
-But when syncing two repos, timestamps are critical at least for my use case. I can't lose this info. Even if it's expensive. 
-
-Appreciate if you can consider to add it for direct mode repos, ie when a file is synced to another repo and created there, it shall carry at least the mtime of the file in source repo. Owncloud sync does it, btsync does it, although I know git-annex is different than those. 
-"""]]
diff --git a/doc/bugs/sync_does_not_preserve_timestamps/comment_3_9a3eeddc46e5a420575f00cb47caf703._comment b/doc/bugs/sync_does_not_preserve_timestamps/comment_3_9a3eeddc46e5a420575f00cb47caf703._comment
deleted file mode 100644
index ba34823d4..000000000
--- a/doc/bugs/sync_does_not_preserve_timestamps/comment_3_9a3eeddc46e5a420575f00cb47caf703._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawmK0703vNSIQsP1mGf-4MAPnsBZiSc6yVo"
- nickname="Emre"
- subject="comment 3"
- date="2014-09-23T21:15:29Z"
- content="""
-Btw, git storing the last commit time as Mtime is not enough, it shall store the original timestamp of the file, not the date of commit. Hope I could explain and hope this is something doable.
-"""]]
diff --git a/doc/bugs/sync_does_not_preserve_timestamps/comment_4_99b064259fc2e3c6eb83c3da3b2d3bac._comment b/doc/bugs/sync_does_not_preserve_timestamps/comment_4_99b064259fc2e3c6eb83c3da3b2d3bac._comment
deleted file mode 100644
index 08de75619..000000000
--- a/doc/bugs/sync_does_not_preserve_timestamps/comment_4_99b064259fc2e3c6eb83c3da3b2d3bac._comment
+++ /dev/null
@@ -1,10 +0,0 @@
-[[!comment format=mdwn
- username="http://svario.it/gioele"
- nickname="gioele"
- subject="comment 4"
- date="2014-09-24T07:15:09Z"
- content="""
-You can try to store the timestamps just before commit and restore them on checkout.
-
-Have a look at [metastore](https://github.com/przemoc/metastore): it is a ready-made solution for plain git. Maybe you can adapt it to git-annex.
-"""]]
diff --git a/doc/bugs/sync_does_not_preserve_timestamps/comment_5_c95c8b9bd617830604500213c962fc7a._comment b/doc/bugs/sync_does_not_preserve_timestamps/comment_5_c95c8b9bd617830604500213c962fc7a._comment
deleted file mode 100644
index 7632548cd..000000000
--- a/doc/bugs/sync_does_not_preserve_timestamps/comment_5_c95c8b9bd617830604500213c962fc7a._comment
+++ /dev/null
@@ -1,9 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawlM_DRhi_5pJrTA0HbApHR25iAgy-NBXTY"
- nickname="Tor Arne"
- subject="comment 5"
- date="2014-10-01T22:02:43Z"
- 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 :/
-
-"""]]
diff --git a/doc/bugs/sync_does_not_preserve_timestamps/comment_6_b99e00d0bc4258c4cb28b544b19ea3b8._comment b/doc/bugs/sync_does_not_preserve_timestamps/comment_6_b99e00d0bc4258c4cb28b544b19ea3b8._comment
deleted file mode 100644
index 67fe25595..000000000
--- a/doc/bugs/sync_does_not_preserve_timestamps/comment_6_b99e00d0bc4258c4cb28b544b19ea3b8._comment
+++ /dev/null
@@ -1,12 +0,0 @@
-[[!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:39:01Z"
- content="""
-Isn't this what the metadata feature does though? http://git-annex.branchable.com/design/metadata/
-
-With annex.genmetadata true set, it should store year and mont (but not day/time? if so why not?
-
-Is the missing piece of the puzzle to apply the metadata again on checkout?
-"""]]