summaryrefslogtreecommitdiff
path: root/doc
diff options
context:
space:
mode:
authorGravatar Joey Hess <joey@kitenet.net>2012-08-26 15:44:32 -0400
committerGravatar Joey Hess <joey@kitenet.net>2012-08-26 15:44:32 -0400
commitbb68f1c5257555614b4b23cceee93a90069f3e07 (patch)
treec39b32bd2fdad477343d9acb99b14251211e31c9 /doc
parentc70f565529feeea116403c359621faf7caffe826 (diff)
update
Diffstat (limited to 'doc')
-rw-r--r--doc/design/assistant/syncing.mdwn9
1 files changed, 5 insertions, 4 deletions
diff --git a/doc/design/assistant/syncing.mdwn b/doc/design/assistant/syncing.mdwn
index ada0f04a6..4a77a5662 100644
--- a/doc/design/assistant/syncing.mdwn
+++ b/doc/design/assistant/syncing.mdwn
@@ -3,10 +3,6 @@ all the other git clones, at both the git level and the key/value level.
## immediate action items
-* The syncing code currently doesn't run for special remotes. While
- transfering the git info about special remotes could be a complication,
- if we assume that's synced between existing git remotes, it should be
- possible for them to do file transfers to/from special remotes.
* Sometimes a Download gets queued from a slow remote, and then a fast
remote becomes available, and a Download is queued from it. Would be
good to sort the transfer queue to run fast Downloads (and Uploads) first.
@@ -206,3 +202,8 @@ redone to check it.
* Often several remotes will be queued for full TransferScanner scans,
and the scan does the same thing for each .. so it would be better to
combine them into one scan in such a case. **done**
+* The syncing code currently doesn't run for special remotes. While
+ transfering the git info about special remotes could be a complication,
+ if we assume that's synced between existing git remotes, it should be
+ possible for them to do file transfers to/from special remotes.
+ **done**