summaryrefslogtreecommitdiff
path: root/doc/todo/parallel_possibilities.mdwn
diff options
context:
space:
mode:
authorGravatar Joey Hess <joey@kitenet.net>2011-02-25 15:54:29 -0400
committerGravatar Joey Hess <joey@kitenet.net>2011-02-25 15:54:29 -0400
commit8aebf9a337e26328c5cb406300fcef5df42bc7b3 (patch)
tree899f14deb5853c1eb7ec035a8c183e085a195ebe /doc/todo/parallel_possibilities.mdwn
parent3f7c0b6970f58c1484615df7b3ec40f3ee44c9df (diff)
update
Diffstat (limited to 'doc/todo/parallel_possibilities.mdwn')
-rw-r--r--doc/todo/parallel_possibilities.mdwn9
1 files changed, 5 insertions, 4 deletions
diff --git a/doc/todo/parallel_possibilities.mdwn b/doc/todo/parallel_possibilities.mdwn
index 15e5171ca..9c0e69e29 100644
--- a/doc/todo/parallel_possibilities.mdwn
+++ b/doc/todo/parallel_possibilities.mdwn
@@ -6,7 +6,8 @@ Anyway, each git-annex command is broken down into a series of independant
actions, which has some potential for parallelism.
Each action has 3 distinct phases, basically "check", "perform", and
-"cleanup". The perform actions are not parellizable; the cleanup may be,
-and the check should be easily parallelizable, although they may access the
-disk or run minor git query commands, so would probably not want to run
-too many of them at once.
+"cleanup". The perform actions are probably parellizable; the cleanup may be
+(but not if it has to run git commands to stage state; it can queue
+commands though); the check should be easily parallelizable, although they
+may access the disk or run minor git query commands, so would probably not
+want to run too many of them at once.