diff options
| author |  Joey Hess <joey@kitenet.net> | 2013-06-12 15:29:45 -0400 |
|---|---|---|
| committer | Joey Hess <joey@kitenet.net> | 2013-06-12 15:29:45 -0400 |
| commit | 6d1a329e89128bc53c45887d77ad4d8646bf34a2 (patch) | |
| tree | 6f52975ef81a1910677d6886a33b432d5ec89fb4 | |
| parent | 349c550e1dc794f10bcd283b1893c10932553a7a (diff) | |
close
| -rw-r--r-- | doc/bugs/True_backup_support.mdwn | 2 |
1 files changed, 2 insertions, 0 deletions
diff --git a/doc/bugs/True_backup_support.mdwn b/doc/bugs/True_backup_support.mdwn index ebf69c617..72fd9fb1f 100644 --- a/doc/bugs/True_backup_support.mdwn +++ b/doc/bugs/True_backup_support.mdwn @@ -3,3 +3,5 @@ I'd like to be able to restore my data from S3/Glacier following a catastrophic 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]] |