diff options
author | https://launchpad.net/~ojwb <Olly_Betts@web> | 2012-05-24 05:07:07 +0000 |
---|---|---|
committer | admin <admin@branchable.com> | 2012-05-24 05:07:07 +0000 |
commit | 09fbc215e8f7cf7aec85c3a68e8ad8c5c3b84b66 (patch) | |
tree | 0bf6c0668f10055f3c3ef1b01e7f2178ebbec716 /doc/todo | |
parent | 66580a8b7ab4aad30a3d615063ddd0efbd35df65 (diff) |
typo fixes
Diffstat (limited to 'doc/todo')
-rw-r--r-- | doc/todo/automatic_bookkeeping_watch_command.mdwn | 8 |
1 files changed, 4 insertions, 4 deletions
diff --git a/doc/todo/automatic_bookkeeping_watch_command.mdwn b/doc/todo/automatic_bookkeeping_watch_command.mdwn index d7a3517a1..4b688b839 100644 --- a/doc/todo/automatic_bookkeeping_watch_command.mdwn +++ b/doc/todo/automatic_bookkeeping_watch_command.mdwn @@ -4,10 +4,10 @@ It would run, in the background, watching via inotify for changes, and automatically annexing new files, etc. The blue sky goal would be something automated like dropbox, except fully -distributed. All files put into the repository would propigate out +distributed. All files put into the repository would propagate out to all the other clones of it, as network links allow. Note that while dropbox allows modifying files, git-annex freezes them upon creation, -so this would not be 100% equivilant to dropbox. --[[Joey]] +so this would not be 100% equivalent to dropbox. --[[Joey]] ---- @@ -25,7 +25,7 @@ Also nice to have would be: - Somehow sync remotes, possibly using a push sync like dvcs-autosync does, so they are immediately updated. -- Somehow get content that is unavilable. This is problimatic with inotify, +- Somehow get content that is unavailable. This is problematic with inotify, since we only get an event once the user has tried (and failed) to read from the file. Perhaps instead, automatically copy content that is added out to remotes, with the goal of all repos eventually getting a copy, @@ -35,7 +35,7 @@ Also nice to have would be: - 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 - its symlink pointed to! Alternatievely, perhaps automatically + its symlink pointed to! Alternatively, perhaps automatically do an expensive unused/dropunused cleanup process. - Support OSes other than Linux; it only uses inotify currently. |