Sat, 05 Dec 2015 22:47:26 -0800 test: rename 'check-code' own test to 'test-contrib-check-code.t'
Pierre-Yves David <pierre-yves.david@fb.com> [Sat, 05 Dec 2015 22:47:26 -0800] rev 27367
test: rename 'check-code' own test to 'test-contrib-check-code.t' This test (making sure the 'check-code' script run as intended) have been confused with the test making that the mercurial code base comply with our coding still by multiple generations of contributors. We are moving it out of the way so that all tests starting with 'test-check' are now doing compliance testing.
Mon, 14 Dec 2015 10:47:27 -0800 parsers: add a missed PyErr_NoMemory
Bryan O'Sullivan <bos@serpentine.com> [Mon, 14 Dec 2015 10:47:27 -0800] rev 27366
parsers: add a missed PyErr_NoMemory
Mon, 14 Dec 2015 10:47:26 -0800 parsers: check results of PyInt_FromLong (issue4771)
Bryan O'Sullivan <bos@serpentine.com> [Mon, 14 Dec 2015 10:47:26 -0800] rev 27365
parsers: check results of PyInt_FromLong (issue4771)
Mon, 14 Dec 2015 10:47:24 -0800 parsers: simplify error logic in compute_phases_map_sets
Bryan O'Sullivan <bos@serpentine.com> [Mon, 14 Dec 2015 10:47:24 -0800] rev 27364
parsers: simplify error logic in compute_phases_map_sets Since Py_XDECREF and free both accept NULL pointers, we can get by with just two exit paths: one for success, and one for error. This considerably simplifies reasoning about the possible ways to exit from this function.
(0) -10000 -3000 -1000 -300 -100 -30 -10 -4 +4 +10 +30 +100 +300 +1000 +3000 +10000 tip