Wed, 11 Nov 2015 13:28:00 -0800 debugdirstate: convert keyword parameters to **opts
Christian Delahousse <cdelahousse@fb.com> [Wed, 11 Nov 2015 13:28:00 -0800] rev 27003
debugdirstate: convert keyword parameters to **opts Removes the named arguments and replaces them by accessing opts. This will be used in the next patch in the series because we'll be adding more flags to debugdirstate
Tue, 17 Nov 2015 18:01:21 -0800 convert: changed test's progress output format to ignore estimate
Christian Delahousse <cdelahousse@fb.com> [Tue, 17 Nov 2015 18:01:21 -0800] rev 27002
convert: changed test's progress output format to ignore estimate On my machine, whenever I run all test with a high -j value, test-convert-git.t would consistently fail by displaying an estimate. This patch removes that value from the output.
Tue, 17 Nov 2015 13:12:33 -0800 mq: use repo._bookmarks.recordchange instead of repo._bookmarks.write
Laurent Charignon <lcharignon@fb.com> [Tue, 17 Nov 2015 13:12:33 -0800] rev 27001
mq: use repo._bookmarks.recordchange instead of repo._bookmarks.write Before this patch, mq was using repo._bookmarks.write. This patch replaces this code with the recommended way of saving bookmarks changes: repo._bookmarks.recordchange.
Tue, 17 Nov 2015 13:12:46 -0800 mq: indentation change to make the next patch more legible
Laurent Charignon <lcharignon@fb.com> [Tue, 17 Nov 2015 13:12:46 -0800] rev 27000
mq: indentation change to make the next patch more legible We put the code to be indented in the next patch in a "if True:" block to make it easier to review.
Tue, 17 Nov 2015 12:49:57 -0800 bookmarks: use repo._bookmarks.recordchange instead of repo._bookmarks.write
Laurent Charignon <lcharignon@fb.com> [Tue, 17 Nov 2015 12:49:57 -0800] rev 26999
bookmarks: use repo._bookmarks.recordchange instead of repo._bookmarks.write We move from the old api repo._bookmarks.write to the new api repo._bookmarks.recordchange.
Wed, 18 Nov 2015 01:36:58 -0800 localrepo: put bookmark move following commit in one transaction
Laurent Charignon <lcharignon@fb.com> [Wed, 18 Nov 2015 01:36:58 -0800] rev 26998
localrepo: put bookmark move following commit in one transaction Before this patch, making a commit on a local repo could move a bookmark and both operations would not be grouped as one transaction. This patch makes both operations part of one transaction. This is necessary to switch to the new api to save bookmarks repo._bookmarks.recordchange if we don't want to change the current behavior of rollback. Dirstate change happening after the commit is done is now part of the transaction mentioned above. This leads to a change in the expected output of several tests. The change to test-fncache happens because both lock are now released in the same finally clause. The lock release is made explicitly buggy in this test. Previously releasing lock would crash triggering release of wlock that crashes too. Now lock release crash does not directly result in the release of wlock. Instead wlock is released at garbage collection time and the error raised at that time "confuses" python.
Tue, 17 Nov 2015 15:43:21 -0800 test-resolve.t: switch to mergestate.read()
Siddharth Agarwal <sid0@fb.com> [Tue, 17 Nov 2015 15:43:21 -0800] rev 26997
test-resolve.t: switch to mergestate.read() See previous patches for why we're doing this.
Tue, 17 Nov 2015 13:58:50 -0800 localrepo.commit: switch to mergestate.read()
Siddharth Agarwal <sid0@fb.com> [Tue, 17 Nov 2015 13:58:50 -0800] rev 26996
localrepo.commit: switch to mergestate.read() See previous patches for why we're doing this.
Tue, 17 Nov 2015 13:57:38 -0800 fileset: switch to mergestate.read()
Siddharth Agarwal <sid0@fb.com> [Tue, 17 Nov 2015 13:57:38 -0800] rev 26995
fileset: switch to mergestate.read() See previous patches for why we're doing this.
Tue, 17 Nov 2015 14:20:55 -0800 commands.summary: switch to mergestate.read()
Siddharth Agarwal <sid0@fb.com> [Tue, 17 Nov 2015 14:20:55 -0800] rev 26994
commands.summary: switch to mergestate.read() See previous patch for why we're doing this. We do this with a bit of care -- it would be bad form for 'hg summary' to abort completely if we encounter an unsupported merge record. Instead just warn about that and continue with the rest of the summary.
(0) -10000 -3000 -1000 -300 -100 -10 +10 +100 +300 +1000 +3000 +10000 tip