Thu, 03 Sep 2009 02:42:56 +0200 manifestdict: remove unnecessary dictionary copy
Benoit Boissinot <benoit.boissinot@ens-lyon.org> [Thu, 03 Sep 2009 02:42:56 +0200] rev 9416
manifestdict: remove unnecessary dictionary copy No need to copy the dict, dict.__init__() will do that for us. It was responsible for a non-negligeable waste of time during a qpush of an -mm queue on the kernel repo.
Wed, 02 Sep 2009 21:05:43 +0200 manifest.add(): cleanup worklist construction and iteration
Benoit Boissinot <benoit.boissinot@ens-lyon.org> [Wed, 02 Sep 2009 21:05:43 +0200] rev 9415
manifest.add(): cleanup worklist construction and iteration
Wed, 02 Sep 2009 21:05:01 +0200 manifest: simplify cache handling, use a unique cache
Benoit Boissinot <benoit.boissinot@ens-lyon.org> [Wed, 02 Sep 2009 21:05:01 +0200] rev 9414
manifest: simplify cache handling, use a unique cache
Wed, 02 Sep 2009 20:18:35 +0200 manifest.add(): simplify with iterators and generator expressions
Benoit Boissinot <benoit.boissinot@ens-lyon.org> [Wed, 02 Sep 2009 20:18:35 +0200] rev 9413
manifest.add(): simplify with iterators and generator expressions
Sat, 29 Aug 2009 00:30:03 +0200 color: do all setup in uisetup
Martin Geisler <mg@lazybytes.net> [Sat, 29 Aug 2009 00:30:03 +0200] rev 9412
color: do all setup in uisetup Now that extensions are loaded in phases, we are guaranteed to always find mq in uisetup with extensions.find and we know that the mq commands are not yet copied into commands.table.
Sun, 16 Aug 2009 00:41:24 +0200 extensions: pass ui arguement to extsetup if accepted
Simon Heimberg <simohe@besonet.ch> [Sun, 16 Aug 2009 00:41:24 +0200] rev 9411
extensions: pass ui arguement to extsetup if accepted
Sat, 29 Aug 2009 00:29:16 +0200 extensions: load and configure extensions in well-defined phases
Martin Geisler <mg@lazybytes.net> [Sat, 29 Aug 2009 00:29:16 +0200] rev 9410
extensions: load and configure extensions in well-defined phases Extensions are now loaded with a call-graph like this: dispatch._dispatch extensions.loadall extensions.load # add foo module to extensions._extensions extensions.load # add bar module to extensions._extensions foo.uisetup(ui) bar.uisetup(ui) foo.extsetup() bar.extsetup() commands.table.update(foo.cmdtable) commands.table.update(bar.cmdtable) hg.repository foo.reposetup(ui, repo) bar.reposetup(ui, repo) The uisetup calls could easily be moved out to dispatch._dispatch, but have been kept in extensions.loadall since at least TortoiseHg calls extensions.loadall and expects it to call uisetup. The extensions.load function called uisetup. It now has an unused ui argument which has been kept for backwards compatibility.
Fri, 28 Aug 2009 22:14:04 +0200 highlight: move code from module top-level into extsetup
Martin Geisler <mg@lazybytes.net> [Fri, 28 Aug 2009 22:14:04 +0200] rev 9409
highlight: move code from module top-level into extsetup
Fri, 28 Aug 2009 20:53:03 +0200 run-tests: standardize on --foo instead of -f/--foo
Martin Geisler <mg@lazybytes.net> [Fri, 28 Aug 2009 20:53:03 +0200] rev 9408
run-tests: standardize on --foo instead of -f/--foo We write -f/--foo in Mercurial help texts (docstrings), but I think it looks strange in error messages.
Fri, 28 Aug 2009 20:50:54 +0200 run-tests: use parser.error for cmdline option errors
Martin Geisler <mg@lazybytes.net> [Fri, 28 Aug 2009 20:50:54 +0200] rev 9407
run-tests: use parser.error for cmdline option errors
(0) -3000 -1000 -300 -100 -10 +10 +100 +300 +1000 +3000 +10000 +30000 tip