updates

diff --git a/doc/design/assistant/inotify.mdwn b/doc/design/assistant/inotify.mdwn
index 3caaaa0e808701feafc9fb6da1e1c529528cb036..11220c2eefa6e96262c3792c3f03f9e84b9dba0c 100644 (file)
--- a/doc/design/assistant/inotify.mdwn
+++ b/doc/design/assistant/inotify.mdwn
@@ -6,14 +6,11 @@ available!
 
 ## known bugs
 
-* When you `git annex unlock` a file, it will immediately be re-locked.
-  See [[bugs/watcher_commits_unlocked_files]].
-
 * Kqueue has to open every directory it watches, so too many directories
   will run it out of the max number of open files (typically 1024), and fail.
   I may need to fork off multiple watcher processes to handle this.
   See [[bug|bugs/Issue_on_OSX_with_some_system_limits]]. (Does not affect
-  OSX any longer).
+  OSX any longer, only other BSDs).
 
 ## todo
 
@@ -28,7 +25,7 @@ available!
 * There needs to be a way for a new version of git-annex, when installed,
   to restart any running watch or assistant daemons. Or for the daemons
   to somehow detect it's been upgraded and restart themselves. Needed
-  to allow for imcompatable changes and, I suppose, for security upgrades..
+  to allow for incompatable changes and, I suppose, for security upgrades..
 
 ## beyond Linux
 
@@ -203,3 +200,5 @@ Many races need to be dealt with by this code. Here are some of them.
 - If a file is checked into git as a normal file and gets modified
   (or merged, etc), it will be converted into an annexed file.
   See [[blog/day_7__bugfixes]]. **done**; we always check ls-files now
+- When you `git annex unlock` a file, it will immediately be re-locked.
+  See [[bugs/watcher_commits_unlocked_files]]. Seems fixed now?

diff --git a/doc/design/assistant/leftovers.mdwn b/doc/design/assistant/leftovers.mdwn
index 2275d5544a003c3cafecd09be0ed957aea4f1d7d..b8c0f456b6d374c2de866cc0ff12352efb8e695b 100644 (file)
--- a/doc/design/assistant/leftovers.mdwn
+++ b/doc/design/assistant/leftovers.mdwn
@@ -8,7 +8,8 @@ Things that don't fit anywhere else:
   are not kept synced, but in some situations (ie, low disk space phones),
   that is likely.
 * Drop files that have not been used lately, or meet some other criteria
-  (as long as there's a copy elsewhere).
+  (as long as there's a copy elsewhere). **done** (via preferred content;
+  eg archive directories)
 * Perhaps automatically dropunused files that have been deleted,
   although I cannot see a way to do that, since by the time the inotify
   deletion event arrives, the file is deleted, and we cannot see what