summaryrefslogtreecommitdiff
path: root/doc
diff options
context:
space:
mode:
authorGravatar Joey Hess <joey@kitenet.net>2012-10-19 14:22:13 -0400
committerGravatar Joey Hess <joey@kitenet.net>2012-10-19 14:22:13 -0400
commit7723c5ea6a09233057813e7f7f582d4764e2b7ae (patch)
treeafc7b285d2a94666dab2a1f2abdc3266a0fdd9aa /doc
parent830c98ee340d7e2ba069e453f73a4049bd639d7f (diff)
check preferred content when a file is moved or created
This can result in the file being dropped, or being downloaded, or even being dropped from some other repo. It's even possible to create a file in a directory where content is not wanted, which will make the assistant immediately send it elsewhere, and then drop it.
Diffstat (limited to 'doc')
-rw-r--r--doc/design/assistant/transfer_control.mdwn7
1 files changed, 3 insertions, 4 deletions
diff --git a/doc/design/assistant/transfer_control.mdwn b/doc/design/assistant/transfer_control.mdwn
index 1c31b85e7..a14b8410f 100644
--- a/doc/design/assistant/transfer_control.mdwn
+++ b/doc/design/assistant/transfer_control.mdwn
@@ -33,10 +33,9 @@ the same content, this gets tricky. Let's assume there are not.)
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.) **done**
-2. renaming of a file (ie, moved to `archive/`)
- (note that renaming a file can also make it become preferred content
- again, and should cause it to be transferred in that case, which doesn't
- happen either..)
+2. renaming of a file (ie, moved to `archive/`) **done**
+ (note also that renaming a file can also make it become preferred content
+ again, and should cause it to be transferred in that case) **done**
3. we get a file (`in`, `copies`) **done**
4. we sent a file (`in`, `copies`) **done**
5. some other repository drops the file (`in`, `copies` .. However, it's