summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorGravatar Joey Hess <joey@kitenet.net>2013-07-31 12:31:30 -0400
committerGravatar Joey Hess <joey@kitenet.net>2013-07-31 12:31:30 -0400
commit1481ef8dbbea17b8b42b856137560e5c28ae368c (patch)
treecbff8abc5a834de503bf61dde8e7c6d8ee8efca9
parenta1bbb16b2a86325e35df1c4799b100dd503cd49d (diff)
make edits that a commenter apparently didn't realize they could make. this is a wiki..
-rw-r--r--doc/backends.mdwn5
1 files changed, 3 insertions, 2 deletions
diff --git a/doc/backends.mdwn b/doc/backends.mdwn
index e1a3da218..4e9776ff0 100644
--- a/doc/backends.mdwn
+++ b/doc/backends.mdwn
@@ -5,12 +5,13 @@ to retrieve the file's content (its value).
Multiple pluggable key-value backends are supported, and a single repository
can use different ones for different files.
-* `SHA256E` -- The default backend for new files. This allows
+* `SHA256E` -- The default backend for new files, combines a SHA256 hash of
+ the file's content with the file's extension. This allows
verifying that the file content is right, and can avoid duplicates of
files with the same content. Its need to generate checksums
can make it slower for large files.
* `SHA256` -- Does not include the file extension in the key, which can
- lead to better deduplication.
+ lead to better deduplication but can confuse some programs.
* `WORM` ("Write Once, Read Many") This assumes that any file with
the same basename, size, and modification time has the same content.
This is the the least expensive backend, recommended for really large