Sun, 21 May 2006 23:07:50 -0700 merge with crew.
Vadim Gelfer <vadim.gelfer@gmail.com> [Sun, 21 May 2006 23:07:50 -0700] rev 2332
merge with crew.
Sun, 21 May 2006 23:07:19 -0700 diff: allow to use -rA:B syntax as well as -rA -rB
Vadim Gelfer <vadim.gelfer@gmail.com> [Sun, 21 May 2006 23:07:19 -0700] rev 2331
diff: allow to use -rA:B syntax as well as -rA -rB
Sun, 21 May 2006 22:14:11 -0700 add 'uisetup' function to extension module protocol.
Vadim Gelfer <vadim.gelfer@gmail.com> [Sun, 21 May 2006 22:14:11 -0700] rev 2330
add 'uisetup' function to extension module protocol. if uisetup functin exists in extension, is called before cmdtable examined. called with ui object as parameter. lets module modify cmdtable before commands.py sees it.
Sat, 20 May 2006 12:52:02 -0700 notify: add debug output. do not fail if no config file.
Vadim Gelfer <vadim.gelfer@gmail.com> [Sat, 20 May 2006 12:52:02 -0700] rev 2329
notify: add debug output. do not fail if no config file. use --debug to see debug output.
Sat, 20 May 2006 15:34:19 -0300 hgweb.manifest: revno of manifest and changelog aren't always the same
Alexis S. L. Carvalho <alexis@cecm.usp.br> [Sat, 20 May 2006 15:34:19 -0300] rev 2328
hgweb.manifest: revno of manifest and changelog aren't always the same In the v4l-dvb repo, the manifest revno and the changelog revno are not in sync. This happened because the same patch was applied to the same revision in two different branches, resulting in the same manifest text, with the same parents and so the first revision was reused. Since hgweb.manifest was assuming the revnos of the manifest and of the changelog were always the same, clicking on manifest -> bz2 in the v4l-dvb site would download the wrong revision. Use the linkrev to go from manifest revision to changelog revision. This still won't be perfect since the page will still talk about "manifest for changeset XYZ", where XYZ was the first changeset to have this manifest, which is not necessarily the same changeset that the user clicked to get to this page - but at least the contents will be the same.
Fri, 19 May 2006 14:58:13 -0700 merge with crew.
Vadim Gelfer <vadim.gelfer@gmail.com> [Fri, 19 May 2006 14:58:13 -0700] rev 2327
merge with crew.
Fri, 19 May 2006 14:57:45 -0700 notify: fix off by one error.
Vadim Gelfer <vadim.gelfer@gmail.com> [Fri, 19 May 2006 14:57:45 -0700] rev 2326
notify: fix off by one error.
Fri, 19 May 2006 08:57:26 -0700 merge with crew.
Vadim Gelfer <vadim.gelfer@gmail.com> [Fri, 19 May 2006 08:57:26 -0700] rev 2325
merge with crew.
Fri, 19 May 2006 08:57:12 -0700 merge with crew.
Vadim Gelfer <vadim.gelfer@gmail.com> [Fri, 19 May 2006 08:57:12 -0700] rev 2324
merge with crew.
Fri, 19 May 2006 08:54:28 -0700 setup.py: install packagescan before any mercurial modules is imported
Volker Kleinfeld <Volker.Kleinfeld@gmx.de> [Fri, 19 May 2006 08:54:28 -0700] rev 2323
setup.py: install packagescan before any mercurial modules is imported Further the installation of packagescan over demandload is moved to the packagescan module. I added as well few more comments in the packagescan module to avoid the wrong use of package scan in the future. Reason: mercurial.packagescan acts as fake mercurial.demandload during a py2exe run. Unfortunatly the import of mercurial.version in setup.py is done before mercurial.packagescan is installed. This results in few imports without mercurial.packagescan in charge and therefore not all dependend modules are detected when running mercurial.packagescan.getmodules later e.g. winerror is missed.
(0) -1000 -300 -100 -10 +10 +100 +300 +1000 +3000 +10000 +30000 tip