bbba6c19bd
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. |
||
---|---|---|
.. | ||
adding_a_remote | ||
moving_file_content_between_repositories | ||
adding_a_remote.mdwn | ||
adding_files.mdwn | ||
backups.mdwn | ||
creating_a_repository.mdwn | ||
fsck:_verifying_your_data.mdwn | ||
fsck:_when_things_go_wrong.mdwn | ||
getting_file_content.mdwn | ||
Internet_Archive_via_S3.mdwn | ||
migrating_data_to_a_new_backend.mdwn | ||
modifying_annexed_files.mdwn | ||
more.mdwn | ||
moving_file_content_between_repositories.mdwn | ||
recover_data_from_lost+found.mdwn | ||
removing_files.mdwn | ||
removing_files:_When_things_go_wrong.mdwn | ||
renaming_files.mdwn | ||
transferring_files:_When_things_go_wrong.mdwn | ||
untrusted_repositories.mdwn | ||
unused_data.mdwn | ||
using_Amazon_S3.mdwn | ||
using_bup.mdwn | ||
using_ssh_remotes.mdwn | ||
using_the_SHA1_backend.mdwn | ||
using_the_web.mdwn | ||
what_to_do_when_you_lose_a_repository.mdwn |