summaryrefslogtreecommitdiff
path: root/doc/tips/using_the_SHA1_backend.mdwn
diff options
context:
space:
mode:
authorGravatar Joey Hess <joey@kitenet.net>2011-10-17 13:56:36 -0400
committerGravatar Joey Hess <joey@kitenet.net>2011-10-17 13:56:36 -0400
commit617bdc740f76e0b5cb8d73a8b122cd2b3e6fe961 (patch)
tree92c932685e19b1df6bd453810e9a4052cdf92f3e /doc/tips/using_the_SHA1_backend.mdwn
parent66fa4c947c30ca9848121912229f3e84a855a74f (diff)
reorg
Diffstat (limited to 'doc/tips/using_the_SHA1_backend.mdwn')
-rw-r--r--doc/tips/using_the_SHA1_backend.mdwn11
1 files changed, 11 insertions, 0 deletions
diff --git a/doc/tips/using_the_SHA1_backend.mdwn b/doc/tips/using_the_SHA1_backend.mdwn
new file mode 100644
index 000000000..70dc2ef75
--- /dev/null
+++ b/doc/tips/using_the_SHA1_backend.mdwn
@@ -0,0 +1,11 @@
+A handy alternative to the default [[backend|backends]] is the
+SHA1 backend. This backend provides more git-style assurance that your data
+has not been damaged. And the checksum means that when you add the same
+content to the annex twice, only one copy need be stored in the backend.
+
+The only reason it's not the default is that it needs to checksum
+files when they're added to the annex, and this can slow things down
+significantly for really big files. To make SHA1 the default, just
+add something like this to `.gitattributes`:
+
+ * annex.backend=SHA1