Mon, 07 Nov 2011 03:14:53 +0100 dispatch: exit with 8-bit exit code
Mads Kiilerich <mads@kiilerich.com> [Mon, 07 Nov 2011 03:14:53 +0100] rev 15439
dispatch: exit with 8-bit exit code The exit code returned from a program to the shell is unsigned 8-bit, but Mercurial would sometimes try to exit with negative numbers or None. sys.exit on Unix will convert that to 8-bit exit codes, but on Windows negative values showed up as 0. The exit code is now explicitly converted to unsigned 8-bit.
Mon, 07 Nov 2011 03:14:53 +0100 tests: don't let time go back before 0 o'clock in bisect3.t
Mads Kiilerich <mads@kiilerich.com> [Mon, 07 Nov 2011 03:14:53 +0100] rev 15438
tests: don't let time go back before 0 o'clock in bisect3.t Windows agree that it was Thu Jan 01 00:00:00 1970 +0000 but it also claims that it was Thu Dec 31 23:59:59 1969 -0000
Mon, 07 Nov 2011 02:49:00 +0100 diff: always use / in paths in diff
Mads Kiilerich <mads@kiilerich.com> [Mon, 07 Nov 2011 02:49:00 +0100] rev 15437
diff: always use / in paths in diff Subrepo diffs would sometimes use backslash on windows.
Mon, 07 Nov 2011 02:49:00 +0100 cmdutil: don't use repr on paths in pathauditor - it looks strange on windows
Mads Kiilerich <mads@kiilerich.com> [Mon, 07 Nov 2011 02:49:00 +0100] rev 15436
cmdutil: don't use repr on paths in pathauditor - it looks strange on windows
Mon, 07 Nov 2011 02:44:04 +0100 tests: make '(esc)' matching in run-tests.py work as intended
Mads Kiilerich <mads@kiilerich.com> [Mon, 07 Nov 2011 02:44:04 +0100] rev 15435
tests: make '(esc)' matching in run-tests.py work as intended The code for match on (esc) lines didn't work, and it would thus always end up emitting another suggestion ... which however would match the old one.
Mon, 07 Nov 2011 13:46:41 -0600 run-tests: replace inline python handling with more native scheme
Matt Mackall <mpm@selenic.com> [Mon, 07 Nov 2011 13:46:41 -0600] rev 15434
run-tests: replace inline python handling with more native scheme Normally changes in tests are reported like this in diffs: $ cat foo - a + b Using -i mode lets us update tests when the new results are correct and/or populate tests with their output. But with the standard doctest framework, inline Python sections in tests changes instead result in a big failure report that's unhelpful. So here, we replace the doctest calls with a simple compile/eval loop.
Mon, 07 Nov 2011 13:46:39 -0600 merge with crew
Matt Mackall <mpm@selenic.com> [Mon, 07 Nov 2011 13:46:39 -0600] rev 15433
merge with crew
(0) -10000 -3000 -1000 -300 -100 -30 -10 -7 +7 +10 +30 +100 +300 +1000 +3000 +10000 +30000 tip