summaryrefslogtreecommitdiff
path: root/doc/bugs/True_backup_support.mdwn
diff options
context:
space:
mode:
Diffstat (limited to 'doc/bugs/True_backup_support.mdwn')
-rw-r--r--doc/bugs/True_backup_support.mdwn7
1 files changed, 0 insertions, 7 deletions
diff --git a/doc/bugs/True_backup_support.mdwn b/doc/bugs/True_backup_support.mdwn
deleted file mode 100644
index 72fd9fb1f..000000000
--- a/doc/bugs/True_backup_support.mdwn
+++ /dev/null
@@ -1,7 +0,0 @@
-I'd like to be able to restore my data from S3/Glacier following a catastrophic loss of information.
-
-As I understand it, git-annex doesn't solve this problem for me because it only stores file *contents* in S3/Glacier. A restore-from-nothing requires both the file contents and also the file names and metadata, which git-annex doesn't store in S3.
-
-I'm still feeling my way around git-annex, but I think it will probably be sufficient for my purposes to set up a cron job to push my annex to github. But I think it would be helpful if git-annex could take care of this automatically.
-
-> Based on the comments, this is [[done]] --[[Joey]]