47250a153a
Ssh connection caching is now enabled automatically by git-annex. Only one ssh connection is made to each host per git-annex run, which can speed some things up a lot, as well as avoiding repeated password prompts. Concurrent git-annex processes also share ssh connections. Cached ssh connections are shut down when git-annex exits. Note: The rsync special remote does not yet participate in the ssh connection caching. |
||
---|---|---|
.. | ||
centralised_repository:_starting_from_nothing | ||
finding_duplicate_files | ||
using_git_annex_with_no_fixed_hostname_and_optimising_ssh | ||
using_gitolite_with_git-annex | ||
visualizing_repositories_with_gource | ||
automatically_getting_files_on_checkout.mdwn | ||
centralised_repository:_starting_from_nothing.mdwn | ||
centralized_git_repository_tutorial.mdwn | ||
finding_duplicate_files.mdwn | ||
Internet_Archive_via_S3.mdwn | ||
migrating_data_to_a_new_backend.mdwn | ||
powerful_file_matching.mdwn | ||
recover_data_from_lost+found.mdwn | ||
untrusted_repositories.mdwn | ||
using_Amazon_S3.mdwn | ||
using_git_annex_with_no_fixed_hostname_and_optimising_ssh.mdwn | ||
using_gitolite_with_git-annex.mdwn | ||
using_the_SHA1_backend.mdwn | ||
using_the_web_as_a_special_remote.mdwn | ||
visualizing_repositories_with_gource.mdwn | ||
what_to_do_when_a_repository_is_corrupted.mdwn | ||
what_to_do_when_you_lose_a_repository.mdwn |