diff options
| author |  https://www.google.com/accounts/o8/id?id=AItOawl9sYlePmv1xK-VvjBdN-5doOa_Xw-jH4U <Richard@web> | 2011-03-27 20:14:47 +0000 |
|---|---|---|
| committer |  admin <admin@branchable.com> | 2011-03-27 20:14:47 +0000 |
| commit | bec63186ea0b9b25e2387685c209578bc316397d (patch) | |
| tree | a4cec83a893818d80f072ec8e2bcb47e5af1c001 | |
| parent | cd451760c33b702616727f91b0364601609491c5 (diff) | |
| -rw-r--r-- | doc/forum/batch_check_on_remote_when_using_copy.mdwn | 3 |
1 files changed, 3 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 index 355d98f04..0f20ab645 100644 --- a/doc/forum/batch_check_on_remote_when_using_copy.mdwn +++ b/doc/forum/batch_check_on_remote_when_using_copy.mdwn @@ -2,4 +2,7 @@ When I copy my local repository with SHA* to a remote repo with SHA*, every sing 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. +Once all checks are done, one single transfer session should be started. Creating new sessions and waiting for TCP's slowstart to get going is a lot less than efficient. + + -- RichiH |