Tue, 14 Jul 2009 16:50:37 -0700 Make patch.diff filelog cache LRU of 20 files. Fixes issue1738.
Brendan Cully <brendan@kublai.com> [Tue, 14 Jul 2009 16:50:37 -0700] rev 9123
Make patch.diff filelog cache LRU of 20 files. Fixes issue1738. 20 files is as fast as 200 for hg diff -r 28015:30103 of mozilla-central. Ideally we'd use util.lrucachefunc, but the interface doesn't quite work.
Tue, 14 Jul 2009 17:12:12 -0300 url: fix use of non-int port in https connections via proxy
Wagner Bruna <wbruna@softwareexpress.com.br> [Tue, 14 Jul 2009 17:12:12 -0300] rev 9122
url: fix use of non-int port in https connections via proxy Complements eef406165507 (issue1725).
Sun, 12 Jul 2009 22:33:00 -0400 test-fetch: fix non-portable sed regex.
Greg Ward <greg-hg@gerg.ca> [Sun, 12 Jul 2009 22:33:00 -0400] rev 9121
test-fetch: fix non-portable sed regex. (s/...\+/.../ appears to be a GNU-ism: this test broke on OS X and NetBSD. Changing \+ to * fixes it, although that is a slightly less strict regex.)
Mon, 13 Jul 2009 20:19:17 +0200 branch heads: optimise computation of branch head cache (issue1734)
Henrik Stuart <hg@hstuart.dk> [Mon, 13 Jul 2009 20:19:17 +0200] rev 9120
branch heads: optimise computation of branch head cache (issue1734) The previous branch heads cache implementation iterated all ancestors for each new revision in the repository, causing a massive slowdown on cloning larger repositories.
Tue, 14 Jul 2009 12:18:22 -0500 Merge with stable
Matt Mackall <mpm@selenic.com> [Tue, 14 Jul 2009 12:18:22 -0500] rev 9119
Merge with stable
Sun, 12 Jul 2009 00:46:43 -0500 cmdutil: fall back to filename if glob expand has errors
Steve Borho <steve@borho.org> [Sun, 12 Jul 2009 00:46:43 -0500] rev 9118
cmdutil: fall back to filename if glob expand has errors On Windows, Mercurial tries to glob expand provided filenames as a convenience to the user. Unfortunately, there are valid filenames which are not valid glob patterns. In those cases, we should fallback to the original provided filename.
Mon, 13 Jul 2009 21:55:17 +0900 inotify: server: explicitely ignore events in subdirs of .hg/ (issue1735)
Nicolas Dumazet <nicdumz.commits@gmail.com> [Mon, 13 Jul 2009 21:55:17 +0900] rev 9117
inotify: server: explicitely ignore events in subdirs of .hg/ (issue1735)
Mon, 13 Jul 2009 16:49:05 +0200 inotify: fix issue1375, add a test.
Nicolas Dumazet <nicdumz.commits@gmail.com> [Mon, 13 Jul 2009 16:49:05 +0200] rev 9116
inotify: fix issue1375, add a test. The biggest problem was the data structure, which did not allow changing a file into a directory or vice versa. This problem is fixed by b55d44719b47. The walk() method also had an issue in this case: - we know 'path' as a directory. inotify server sleeps. - 'path' is deleted - 'path' is recreated as a file - the server catches up here, and see the deletion. it instantiates a scan(), which in its turn calls for walk(repo, path). - walk() then assumes that 'path' is a directory and calls os.listdir on it, which raises an OSError(errno.ENOTDIR) Catch the error, and yield the file instead of the directory contents.
Tue, 26 May 2009 23:00:35 +0900 inotify: server: new data structure to keep track of changes.
Nicolas Dumazet <nicdumz.commits@gmail.com> [Tue, 26 May 2009 23:00:35 +0900] rev 9115
inotify: server: new data structure to keep track of changes. == Rationale for the new structure == Current structure was a dictionary tree. One directory was tracked as a dictionary: - keys: file/subdir name - values: - for a file, the status (a/r/m/...) - for a subdir, the directory representing the subdir It allowed efficient lookups, no matter of the type of the terminal leaf: for part in path.split('/'): tree = tree[part] However, there is no way to represent a directory and a file with the same name because keys are conflicting in the dictionary. Concrete example: Initial state: root dir |- foo (file) |- bar (file) # data state is: {'foo': 'n', 'bar': 'n'} Remove foo: root dir |- bar (file) # Data becomes {'foo': 'r'} until next commit. Add foo, as a directory, and foo/barbar file: root dir |- bar (file) |-> foo (dir) |- barbar (file) # New state should be represented as: {'foo': {'barbar': 'a'}, 'bar': 'n'} however, the key "foo" is already used and represents the old file. The dirstate: D foo A foo/barbar cannot be represented, hence the need for a new structure. == The new structure == 'directory' class. Represents one directory level. * Notable attributes: Two dictionaries: - 'files' Maps filename -> status for the current dir. - 'dirs' Maps subdir's name -> directory object representing the subdir * methods - walk(), formerly server.walk - lookup(), old server.lookup - dir(), old server.dir This new class allows embedding all the tree walks/lookups in its own class, instead of having everything mixed together in server. Incidently, since files and directories are not stored in the same dictionaries, we are solving the previous key conflict problem. The small drawback is that lookup operation is a bit more complex: for a path a/b/c/d/e we have to check twice the leaf, if e is a directory or a file.
Sun, 12 Jul 2009 21:41:12 +0200 merge with crew-stable
Martin Geisler <mg@lazybytes.net> [Sun, 12 Jul 2009 21:41:12 +0200] rev 9114
merge with crew-stable
Sun, 12 Jul 2009 21:37:24 +0200 gitweb, monoblue: fix double-spacing in file view (issue1733)
Martin Geisler <mg@lazybytes.net> [Sun, 12 Jul 2009 21:37:24 +0200] rev 9113
gitweb, monoblue: fix double-spacing in file view (issue1733) The error was introduced in 338412820a57.
Fri, 10 Jul 2009 17:54:04 +0200 util: use propertycache in opener instead of __getattr__
Simon Heimberg <simohe@besonet.ch> [Fri, 10 Jul 2009 17:54:04 +0200] rev 9112
util: use propertycache in opener instead of __getattr__
Fri, 10 Jul 2009 23:24:35 +0200 mq: use ui.status when pushing and popping patches
Martin Geisler <mg@lazybytes.net> [Fri, 10 Jul 2009 23:24:35 +0200] rev 9111
mq: use ui.status when pushing and popping patches
Thu, 09 Jul 2009 23:59:03 +0200 mq: qpop now tells which patches are popped
Mads Kiilerich <mads@kiilerich.com> [Thu, 09 Jul 2009 23:59:03 +0200] rev 9110
mq: qpop now tells which patches are popped When navigating through a patch series by qpushing and qpopping it was easy to get lost because qpop was silent. I found myself often running qnext after qpop to see which patch I just dropped - especially if I was about to qrm it. This patch makes qpop more symmetric to qpush by showing which patches are applied/"unapplied". I think it is a good change even though it changes output by adding a new line of output.
Fri, 10 Jul 2009 12:49:29 +0200 merge with crew-stable
Martin Geisler <mg@lazybytes.net> [Fri, 10 Jul 2009 12:49:29 +0200] rev 9109
merge with crew-stable
(0) -3000 -1000 -300 -100 -15 +15 +100 +300 +1000 +3000 +10000 +30000 tip