Mon, 04 May 2009 21:18:33 +0900 inotify: Clarify the use of "watcher" name.
Nicolas Dumazet <nicdumz.commits@gmail.com> [Mon, 04 May 2009 21:18:33 +0900] rev 8335
inotify: Clarify the use of "watcher" name. Currently, Watcher is a class in inotify.linux.watcher, but it's also a class in inotify.server . To complicate things further more, the latter has a 'watcher' attribute, an instance of the former class. When it comes to the 'watcher' attribute of the Server class in inotify.server, one can get quite confused: is it a Watcher object from inotify.server, or from inotify.linux.watcher? Changes: * in inotify.linux.watcher : nothing * in inotify.server : ** Watcher class is renamed to RepoWatcher ** server.watcher is renamed to server.repowatcher
Mon, 04 May 2009 18:23:05 +0900 inotify: inotify.server.walk() filetype is never used, do not yield it
Nicolas Dumazet <nicdumz.commits@gmail.com> [Mon, 04 May 2009 18:23:05 +0900] rev 8334
inotify: inotify.server.walk() filetype is never used, do not yield it
Mon, 04 May 2009 20:26:27 +0200 allow http authentication information to be specified in the configuration
Sune Foldager <cryo@cyanite.org> [Mon, 04 May 2009 20:26:27 +0200] rev 8333
allow http authentication information to be specified in the configuration
(0) -3000 -1000 -300 -100 -30 -10 -3 +3 +10 +30 +100 +300 +1000 +3000 +10000 +30000 tip