diff options
| author |  Joey Hess <joey@kitenet.net> | 2011-08-28 16:28:38 -0400 |
|---|---|---|
| committer | Joey Hess <joey@kitenet.net> | 2011-08-28 16:28:38 -0400 |
| commit | bbba6c19bd03f2b4a4ce8a38a2423c794826b1c5 (patch) | |
| tree | 56f50f9c23018f5c4479a0503e1e6c9dcd57c83e /doc/copies.mdwn | |
| parent | 999d5df90b013a7cc8a390c940785118400faf8a (diff) | |
update documentation for new, neutered key-value backends
Backends are now only used to generate keys (and check them); they
are not arbitrary key-value stores for data, because it turned out such
a store is better modeled as a special remote. Updated docs to not
imply backends do more than they do now.
Sometimes I'm tempted to rename "backend" to "keytype" or something,
which would really be more clear. But it would be an annoying transition
for users, with annex.backends etc.
Diffstat (limited to 'doc/copies.mdwn')
| -rw-r--r-- | doc/copies.mdwn | 6 |
1 files changed, 3 insertions, 3 deletions
diff --git a/doc/copies.mdwn b/doc/copies.mdwn index 16eba19c8..93cbd8ea8 100644 --- a/doc/copies.mdwn +++ b/doc/copies.mdwn @@ -1,8 +1,8 @@ -The WORM and SHA1 key-value [[backends]] store data inside -your git repository's `.git` directory, not in some external data store. +Annexed data is stored inside your git repository's `.git/annex` directory. +Some [[special_remotes]] can store annexed data elsewhere. It's important that data not get lost by an ill-considered `git annex drop` -command. So, then using those backends, git-annex can be configured to try +command. So, git-annex can be configured to try to keep N copies of a file's content available across all repositories. (Although [[untrusted_repositories|trust]] don't count toward this total.) |