summaryrefslogtreecommitdiff
path: root/doc
diff options
context:
space:
mode:
authorGravatar Joey Hess <joey@kitenet.net>2012-10-18 14:55:59 -0400
committerGravatar Joey Hess <joey@kitenet.net>2012-10-18 15:07:11 -0400
commitb9138b54db85610ce16d31ef1d1e74c18ee25b87 (patch)
treef98729b435cf14cbf18f3011ae4de01b4eb4fb03 /doc
parent3e657d3db6bc65ab09343eb019ce5bf73666213e (diff)
drop unwanted content in the transfer scan
This was complicated quite a bit by needing to check numcopies. I optimised that, so it only looks up numcopies once per file, no matter how many remotes it checks to drop from. Although it did just occur to me that it might be better to first check if it wants to drop content, and only then check numcopies..
Diffstat (limited to 'doc')
-rw-r--r--doc/design/assistant/transfer_control.mdwn2
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/design/assistant/transfer_control.mdwn b/doc/design/assistant/transfer_control.mdwn
index 8f8dad556..54b7a30c2 100644
--- a/doc/design/assistant/transfer_control.mdwn
+++ b/doc/design/assistant/transfer_control.mdwn
@@ -30,7 +30,7 @@ the same content, this gets tricky. Let's assume there are not.)
1. The preferred content expression can change, or a new repo is added, or
groups change. Generally, some change to global annex state. Only way to deal
with this is an expensive scan. (The rest of the items below come from
- analizing the terminals used in preferred content expressions.)
+ analizing the terminals used in preferred content expressions.) **done**
2. renaming of a file (ie, moved to `archive/`)
3. some other repository gets the file (`in`, `copies`)
4. some other repository drops the file (`in`, `copies` .. However, it's