summaryrefslogtreecommitdiff
path: root/doc/design/assistant/transfer_control.mdwn
diff options
context:
space:
mode:
authorGravatar Joey Hess <joey@kitenet.net>2012-10-18 15:22:28 -0400
committerGravatar Joey Hess <joey@kitenet.net>2012-10-18 15:22:28 -0400
commit3e369ace228e984224c417c6f3524f0b4f5900ac (patch)
tree01811ab6f0a1d49bd83a66ddbe556c0406fa81e8 /doc/design/assistant/transfer_control.mdwn
parentb9138b54db85610ce16d31ef1d1e74c18ee25b87 (diff)
split
Diffstat (limited to 'doc/design/assistant/transfer_control.mdwn')
-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 54b7a30c2..390812320 100644
--- a/doc/design/assistant/transfer_control.mdwn
+++ b/doc/design/assistant/transfer_control.mdwn
@@ -32,7 +32,7 @@ the same content, this gets tricky. Let's assume there are not.)
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/`)
-3. some other repository gets the file (`in`, `copies`)
+3. we get a file (`in`, `copies`)
4. some other repository drops the file (`in`, `copies` .. However, it's
unlikely that an expression would prefer content when *more* copies
exisited, and want to drop it when less do. That's nearly a pathological