Sat, 23 May 2009 12:31:28 -0500 Merge with crew-stable
Matt Mackall <mpm@selenic.com> [Sat, 23 May 2009 12:31:28 -0500] rev 8560
Merge with crew-stable
Sat, 23 May 2009 19:57:25 +0200 windows: make openhardlinks work
Henrik Stuart <hg@hstuart.dk> [Sat, 23 May 2009 19:57:25 +0200] rev 8559
windows: make openhardlinks work Despite the intention, openhardlinks would always evaluate to False.
Sat, 23 May 2009 11:53:23 -0500 revlog: fix reading of larger revlog indices on Windows
Matt Mackall <mpm@selenic.com> [Sat, 23 May 2009 11:53:23 -0500] rev 8558
revlog: fix reading of larger revlog indices on Windows
Fri, 08 May 2009 12:19:57 +0900 inotify: Removing the unnecessary "inotifyserver" class variable.
Nicolas Dumazet <nicdumz.commits@gmail.com> [Fri, 08 May 2009 12:19:57 +0900] rev 8557
inotify: Removing the unnecessary "inotifyserver" class variable.
Wed, 06 May 2009 01:40:03 +0900 inotify: set a flag so a failed inotify query doesn't get repeated.
Nicolas Dumazet <nicdumz.commits@gmail.com> [Wed, 06 May 2009 01:40:03 +0900] rev 8556
inotify: set a flag so a failed inotify query doesn't get repeated. If, for some reason, we can't get the inotify server to start, it's better to disable inotify queries for the instance to avoid trying over and over to start the server, which takes time. Just fall back on repo.status()
Wed, 22 Apr 2009 00:37:35 +0900 inotify: introduce debuginotify, which lists which paths are under watch
Nicolas Dumazet <nicdumz.commits@gmail.com> [Wed, 22 Apr 2009 00:37:35 +0900] rev 8555
inotify: introduce debuginotify, which lists which paths are under watch
Wed, 22 Apr 2009 00:23:40 +0900 inotify: put STAT-specific query answer generation part in its own method
Nicolas Dumazet <nicdumz.commits@gmail.com> [Wed, 22 Apr 2009 00:23:40 +0900] rev 8554
inotify: put STAT-specific query answer generation part in its own method
Fri, 17 Apr 2009 20:10:47 +0900 inotify: change protocol so that different query types can be supported.
Nicolas Dumazet <nicdumz.commits@gmail.com> [Fri, 17 Apr 2009 20:10:47 +0900] rev 8553
inotify: change protocol so that different query types can be supported.
Tue, 07 Apr 2009 19:30:01 +0900 inotify: Separate query sending logic from Server starting.
Nicolas Dumazet <nicdumz.commits@gmail.com> [Tue, 07 Apr 2009 19:30:01 +0900] rev 8552
inotify: Separate query sending logic from Server starting. Use a decorator around the public statusquery method of Client: start_server(query_to_server): try: query_to_server() except QueryFailed: [error recovery, inotify Server (re)starting] query_to_server() This way, introducing a new xxxquery Client method is easy: one has only to code the protocol part of xxxquery, ignoring errors, and decorating it using start_server to handle server recovery and (re)starts
Tue, 07 Apr 2009 18:39:34 +0900 inotify: modular architecture for inotify clients
Nicolas Dumazet <nicdumz.commits@gmail.com> [Tue, 07 Apr 2009 18:39:34 +0900] rev 8551
inotify: modular architecture for inotify clients Put the socket init, query generation and response analysis in a more generic client class.
(0) -3000 -1000 -300 -100 -10 +10 +100 +300 +1000 +3000 +10000 +30000 tip