From 1c9cab56aef888ac598ee8261cf47409dc3954aa Mon Sep 17 00:00:00 2001
From: 
 "https://www.google.com/accounts/o8/id?id=AItOawmUJBh1lYmvfCCiGr3yrdx-QhuLCSRnU5c"
 <Justin@web>
Date: Wed, 1 May 2013 02:22:27 +0000
Subject:

---
 doc/bugs/True_backup_support.mdwn | 5 +++++
 1 file changed, 5 insertions(+)
 create mode 100644 doc/bugs/True_backup_support.mdwn

diff --git a/doc/bugs/True_backup_support.mdwn b/doc/bugs/True_backup_support.mdwn
new file mode 100644
index 000000000..ebf69c617
--- /dev/null
+++ b/doc/bugs/True_backup_support.mdwn
@@ -0,0 +1,5 @@
+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.
-- 
cgit v1.2.3