diff options
| author |  Joey Hess <joey@kitenet.net> | 2012-08-29 13:05:46 -0400 |
|---|---|---|
| committer | Joey Hess <joey@kitenet.net> | 2012-08-29 13:05:46 -0400 |
| commit | cc94ff2d1ddac6ad1a3ab76993b310cdcbf6818c (patch) | |
| tree | 6aac2c1e1f7fd1b5537237f01234b82ec0e58f4f | |
| parent | 3a091926311037fc138a1a56e9de996166c89426 (diff) | |
remove todo about behavior that turns out to be desired
Drives that are not mounted still have Remotes, and it makes sense to scan
them along with all the other remotes on startup, so we end up with queued
transfers for them, that will be used when they get mounted.
| -rw-r--r-- | doc/design/assistant/syncing.mdwn | 2 |
1 files changed, 0 insertions, 2 deletions
diff --git a/doc/design/assistant/syncing.mdwn b/doc/design/assistant/syncing.mdwn index 22827bece..7b652f80b 100644 --- a/doc/design/assistant/syncing.mdwn +++ b/doc/design/assistant/syncing.mdwn @@ -13,8 +13,6 @@ all the other git clones, at both the git level and the key/value level. 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. Or, solve this along with the item above? -* For some reason, the TransferScanner is queueing transfers from remotes - that are on drives that are not mounted. (In my sound repo.) * Ensure that when a remote receives content, and updates its location log, it syncs that update back out. Prerequisite for: * After git sync, identify new content that we don't have that is now available |