diff options
| author |  https://www.google.com/accounts/o8/id?id=AItOawl9sYlePmv1xK-VvjBdN-5doOa_Xw-jH4U <Richard@web> | 2011-03-27 20:11:20 +0000 |
|---|---|---|
| committer |  admin <admin@branchable.com> | 2011-03-27 20:11:20 +0000 |
| commit | cd451760c33b702616727f91b0364601609491c5 (patch) | |
| tree | 19c60fd7e85bd68b4e18d840ab5d102a7a329217 | |
| parent | 1fccea5154ac5b8e10fa387e2230e3a4103cef3b (diff) | |
| -rw-r--r-- | doc/forum/batch_check_on_remote_when_using_copy.mdwn | 5 |
1 files changed, 5 insertions, 0 deletions
diff --git a/doc/forum/batch_check_on_remote_when_using_copy.mdwn b/doc/forum/batch_check_on_remote_when_using_copy.mdwn new file mode 100644 index 000000000..355d98f04 --- /dev/null +++ b/doc/forum/batch_check_on_remote_when_using_copy.mdwn @@ -0,0 +1,5 @@ +When I copy my local repository with SHA* to a remote repo with SHA*, every single file is checked by itself which seems rather inefficient. When my remote is accessed via ssh, git-annex opens a new connections for every check. If you are not using a ssh key or key agent, this gets tedious... + +For all locked files, either git's built-in mechanisms should be used or, if that's not possible, a few hundred checksums (assuming SHA* backend) should be transfered at once and then checked locally before deciding that to transfer. + +-- RichiH |