diff options
author | 2012-07-08 20:53:50 +0200 | |
---|---|---|
committer | 2012-07-08 13:04:35 -0600 | |
commit | 619297e1a7ba89f50fa5be9d7dfdfe5a9510129a (patch) | |
tree | 425a9931a9caa211ae24f9d8c05976757c2203a6 /doc/design/assistant/blog/day_8__speed.mdwn | |
parent | b64a489a07f5e5be5b722ec3b942f505756ce853 (diff) |
Fix typos on blog
Diffstat (limited to 'doc/design/assistant/blog/day_8__speed.mdwn')
-rw-r--r-- | doc/design/assistant/blog/day_8__speed.mdwn | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/design/assistant/blog/day_8__speed.mdwn b/doc/design/assistant/blog/day_8__speed.mdwn index 56b1e9c07..d99add97a 100644 --- a/doc/design/assistant/blog/day_8__speed.mdwn +++ b/doc/design/assistant/blog/day_8__speed.mdwn @@ -16,7 +16,7 @@ quickly is really only important so people don't think it's a resource hog. First impressions are important. :) But what does "made recently" mean exactly? Well, my answer is possibly -overengineered, but most of it is really groundwork for things I'll need +over engineered, but most of it is really groundwork for things I'll need later anyway. I added a new data structure for tracking the status of the daemon, which is periodically written to disk by another thread (thread #6!) to `.git/annex/daemon.status` Currently it looks like this; I anticipate |