summaryrefslogtreecommitdiff
path: root/doc/not
diff options
context:
space:
mode:
authorGravatar http://joeyh.name/ <http://joeyh.name/@web>2013-12-11 15:40:35 +0000
committerGravatar admin <admin@branchable.com>2013-12-11 15:40:35 +0000
commit942b629228ee15940e6818eb44d70f2c0efa52de (patch)
tree96441fa787e8142bfeb98c5ddd7783e436cbb5ef /doc/not
parent535cc9142af7de078117d307166f939bffc10e99 (diff)
Added a comment
Diffstat (limited to 'doc/not')
-rw-r--r--doc/not/comment_10_d8fb9add7e98dadea2a39f8827f75447._comment10
1 files changed, 10 insertions, 0 deletions
diff --git a/doc/not/comment_10_d8fb9add7e98dadea2a39f8827f75447._comment b/doc/not/comment_10_d8fb9add7e98dadea2a39f8827f75447._comment
new file mode 100644
index 000000000..ad7b699f9
--- /dev/null
+++ b/doc/not/comment_10_d8fb9add7e98dadea2a39f8827f75447._comment
@@ -0,0 +1,10 @@
+[[!comment format=mdwn
+ username="http://joeyh.name/"
+ ip="209.250.56.87"
+ subject="comment 10"
+ date="2013-12-11T15:40:35Z"
+ content="""
+@Zellyn, what you describe does not sound unreasonable. But it's hard to say if it's a backup. For example, if you delete a file from the archive folder, and that happened to be the only copy of the file, it's gone.
+
+It's definitely possible to use git-annex in backup-like ways, but what I want to discourage is users thinking that just putting files into git-annex means that they have a backup. Proper backups need to be designed, and tested. It helps to use software that is explicitly designed as a backup solution. git-annex is more about file distribution, and some archiving, than backups.
+"""]]