Sat, 02 Aug 2014 21:46:26 +0900 cmdutil: introduce 'editform' to distinguish the purpose of commit text editing
FUJIWARA Katsunori <foozy@lares.dti.ne.jp> [Sat, 02 Aug 2014 21:46:26 +0900] rev 21999
cmdutil: introduce 'editform' to distinguish the purpose of commit text editing This information will be used to switch '[committemplate] changeset' definition according to its purpose in the subsequent patch. This information also makes it easier to hook commit text editing only in the specific cases.
Tue, 22 Jul 2014 22:40:16 -0700 log: allow patterns with -f
Durham Goode <durham@fb.com> [Tue, 22 Jul 2014 22:40:16 -0700] rev 21998
log: allow patterns with -f It's not uncommon for a user to want to run log with a pattern or directory name on the history of their current commit. Currently we prevent that, but I can't think of any reason to continue blocking that. This commit removes the restriction and allows 'hg log -f <dir/pat>'
Mon, 28 Jul 2014 19:48:59 -0400 run-tests: fix test result counts with --keyword specified or skips occurring
Augie Fackler <raf@durin42.com> [Mon, 28 Jul 2014 19:48:59 -0400] rev 21997
run-tests: fix test result counts with --keyword specified or skips occurring This preserves the current behavior that excludes ignored or skipped tests from the number of tests run, except when tests are ignored due to the --retest flag.
Tue, 29 Jul 2014 22:35:59 -0400 test-run-tests.t: add tests for skips
Augie Fackler <raf@durin42.com> [Tue, 29 Jul 2014 22:35:59 -0400] rev 21996
test-run-tests.t: add tests for skips This will make some minor behavior changes in a future patch more obvious.
Mon, 28 Jul 2014 20:54:14 -0400 test-run-tests.t: add extra data to tests for keyword tests
Augie Fackler <raf@durin42.com> [Mon, 28 Jul 2014 20:54:14 -0400] rev 21995
test-run-tests.t: add extra data to tests for keyword tests This adds a fair amount of overall instability in the enclosing .t. As such, this is performed in its own commit, and a test for --keyword on run-tests.t will be added in a followup change.
Mon, 04 Aug 2014 15:24:57 -0500 purge: drop stat import
Matt Mackall <mpm@selenic.com> [Mon, 04 Aug 2014 15:24:57 -0500] rev 21994
purge: drop stat import
Mon, 04 Aug 2014 14:42:24 -0500 run-tests: add iolock to failure output
Matt Mackall <mpm@selenic.com> [Mon, 04 Aug 2014 14:42:24 -0500] rev 21993
run-tests: add iolock to failure output
Mon, 04 Aug 2014 14:32:34 -0500 merge with stable
Matt Mackall <mpm@selenic.com> [Mon, 04 Aug 2014 14:32:34 -0500] rev 21992
merge with stable
Fri, 01 Aug 2014 13:09:06 -0500 color: pass on key error for win32 (issue4298) stable
Sean Farley <sean.michael.farley@gmail.com> [Fri, 01 Aug 2014 13:09:06 -0500] rev 21991
color: pass on key error for win32 (issue4298) This is a quick fix for some consoles on windows (consoles that are not mingw based) so that the debugcolor command doesn't throw a KeyError when effects aren't supported (e.g. italic).
Fri, 01 Aug 2014 18:30:18 -0700 context: call normal on the right object stable
Siddharth Agarwal <sid0@fb.com> [Fri, 01 Aug 2014 18:30:18 -0700] rev 21990
context: call normal on the right object dirstate.normal is the method that marks files as unchanged/normal. Rev 20a30cd41d21 started caching dirstate.normal in order to improve performance. However, there was an error in the patch: taking the wlock, under some conditions depending on platform, can cause a new dirstate object to be created. Caching dirstate.normal before calling wlock would then cause the fixup calls below to be on the old dirstate object, effectively disappearing into the ether. On Unix and Unix-like OSes, the condition under which we create a new dirstate object is 'the dirstate file has been modified since the last time we opened it'. This happens pretty rarely, so the object is usually the same -- there's little impact. On Windows, the condition is 'always'. This means files in the lookup state are never marked normal, so the bug has a serious performance impact since all the files in the lookup state are re-read every time hg status is run.
Sat, 31 May 2014 16:48:29 -0700 getbundle: add a ``cg`` boolean argument to control changegroup inclusion
Pierre-Yves David <pierre-yves.david@fb.com> [Sat, 31 May 2014 16:48:29 -0700] rev 21989
getbundle: add a ``cg`` boolean argument to control changegroup inclusion The ``getbundle`` function was initially design to return a changegroup bundle. However, bundle2 allows transmitting a wide range of data. Some bundle2 requests may not include a changegroup at all. Before this changeset, the client would request a changegroup for ``heads=[nullid]`` and receive an empty changegroup. We introduce an official boolean parameter, ``cg``, that can be set to false to disable changegroup generation on getbundle. A new bundle2 capability is introduced to let the client know.
Thu, 22 May 2014 17:20:52 -0700 wireproto: add a ``boolean`` type for getbundle parameters
Pierre-Yves David <pierre-yves.david@fb.com> [Thu, 22 May 2014 17:20:52 -0700] rev 21988
wireproto: add a ``boolean`` type for getbundle parameters This will be used to control inclusion of some parts in a bundle2.
Sun, 03 Aug 2014 19:19:23 +0900 i18n: detect UI language without POSIX-style locale variable on Windows (BC)
Yuya Nishihara <yuya@tcha.org> [Sun, 03 Aug 2014 19:19:23 +0900] rev 21987
i18n: detect UI language without POSIX-style locale variable on Windows (BC) On Windows, it isn't common to set LANG environment variable. This patch makes gettext honor Windows-style UI language [1] if no locale variables are set. Because of this change, LANG=C or HGPLAIN must be set in order to disable translation on non-English Windows. [1]: http://msdn.microsoft.com/en-us/library/dd374098(v=VS.85).aspx
Fri, 01 Aug 2014 22:16:54 -0700 locate: use ctx.matches instead of ctx.walk
Siddharth Agarwal <sid0@fb.com> [Fri, 01 Aug 2014 22:16:54 -0700] rev 21986
locate: use ctx.matches instead of ctx.walk On mozilla-central, which is around 100,000 files, best of 5: $ hg --time locate > /dev/null before: real 1.460 secs (user 1.140+0.000 sys 0.320+0.000) after: real 0.620 secs (user 0.610+0.000 sys 0.020+0.000) $ hg --time locate README > /dev/null before: real 0.630 secs (user 0.330+0.000 sys 0.290+0.000) after: real 0.120 secs (user 0.110+0.000 sys 0.020+0.000) Larger repositories see correspondingly larger performance gains.
(0) -10000 -3000 -1000 -300 -100 -14 +14 +100 +300 +1000 +3000 +10000 +30000 tip