From 619297e1a7ba89f50fa5be9d7dfdfe5a9510129a Mon Sep 17 00:00:00 2001 From: Richard Hartmann Date: Sun, 8 Jul 2012 20:53:50 +0200 Subject: Fix typos on blog --- doc/design/assistant/blog/day_25__transfer_queueing.mdwn | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) (limited to 'doc/design/assistant/blog/day_25__transfer_queueing.mdwn') diff --git a/doc/design/assistant/blog/day_25__transfer_queueing.mdwn b/doc/design/assistant/blog/day_25__transfer_queueing.mdwn index 35922c0d1..b07e4592e 100644 --- a/doc/design/assistant/blog/day_25__transfer_queueing.mdwn +++ b/doc/design/assistant/blog/day_25__transfer_queueing.mdwn @@ -6,7 +6,7 @@ Details follow.. Made the committer thread queue Upload Transfers when new files are added to the annex. Currently it tries to transfer the new content -to *every* remote; this innefficiency needs to be addressed later. +to *every* remote; this inefficiency needs to be addressed later. Made the watcher thread queue Download Transfers when new symlinks appear that point to content we don't have. Typically, that will happen @@ -30,12 +30,12 @@ all the assistant's other threads from entering that monad while a transfer is running. This is also necessary to allow multiple concurrent transfers to run in the future. -This is a very tricky peice of code, because that thread will modify the +This is a very tricky piece of code, because that thread will modify the git-annex branch, and its parent thread has to invalidate its cache in order to see any changes the child thread made. Hopefully that's the extent of the complication of doing this. The only reason this was possible at all is that git-annex already support multiple concurrent processes running -and all making independant changes to the git-annex branch, etc. +and all making independent changes to the git-annex branch, etc. After all my groundwork this week, file content transferring is now fully working! -- cgit v1.2.3