Thu, 14 Jun 2018 15:08:32 -0700 tag: use context manager for locks
Martin von Zweigbergk <martinvonz@google.com> [Thu, 14 Jun 2018 15:08:32 -0700] rev 38332
tag: use context manager for locks Differential Revision: https://phab.mercurial-scm.org/D3746
Thu, 14 Jun 2018 15:05:14 -0700 commit: use context manager for locks
Martin von Zweigbergk <martinvonz@google.com> [Thu, 14 Jun 2018 15:05:14 -0700] rev 38331
commit: use context manager for locks Differential Revision: https://phab.mercurial-scm.org/D3745
Thu, 14 Jun 2018 15:08:19 -0700 backout: use context manager for locks
Martin von Zweigbergk <martinvonz@google.com> [Thu, 14 Jun 2018 15:08:19 -0700] rev 38330
backout: use context manager for locks Differential Revision: https://phab.mercurial-scm.org/D3744
Thu, 14 Jun 2018 15:28:32 -0700 backout: use context manager for dirstateguard
Martin von Zweigbergk <martinvonz@google.com> [Thu, 14 Jun 2018 15:28:32 -0700] rev 38329
backout: use context manager for dirstateguard Differential Revision: https://phab.mercurial-scm.org/D3743
Thu, 14 Jun 2018 15:26:18 -0700 backout: use context manager for config override
Martin von Zweigbergk <martinvonz@google.com> [Thu, 14 Jun 2018 15:26:18 -0700] rev 38328
backout: use context manager for config override Differential Revision: https://phab.mercurial-scm.org/D3742
Thu, 14 Jun 2018 15:46:31 -0700 update: use context manager for config override (API)
Martin von Zweigbergk <martinvonz@google.com> [Thu, 14 Jun 2018 15:46:31 -0700] rev 38327
update: use context manager for config override (API) Note that update wasn't resetting the value before, so any extensions that called commands.update() and relied on ui.forcemerge being set after it returned would now have to set it themselves. (There technically a small API change in all of the patches in this series, I believe: If extensions relied on the methods to *clear* ui.forcemerge, then they would have to do that themselves now, because ui.configoverride() actually restores the previous config, it doesn't just clear it like these functions did before.) Differential Revision: https://phab.mercurial-scm.org/D3741
Thu, 14 Jun 2018 15:46:17 -0700 resolve: use context manager for config override
Martin von Zweigbergk <martinvonz@google.com> [Thu, 14 Jun 2018 15:46:17 -0700] rev 38326
resolve: use context manager for config override Differential Revision: https://phab.mercurial-scm.org/D3740
Thu, 14 Jun 2018 15:45:45 -0700 merge: use context manager for config override
Martin von Zweigbergk <martinvonz@google.com> [Thu, 14 Jun 2018 15:45:45 -0700] rev 38325
merge: use context manager for config override Differential Revision: https://phab.mercurial-scm.org/D3739
Thu, 14 Jun 2018 15:45:16 -0700 graft: use context manager for config override
Martin von Zweigbergk <martinvonz@google.com> [Thu, 14 Jun 2018 15:45:16 -0700] rev 38324
graft: use context manager for config override Differential Revision: https://phab.mercurial-scm.org/D3738
Thu, 14 Jun 2018 11:49:10 -0400 tests: suppress read(-1) -> '' calls in fileobjectobserver
Augie Fackler <augie@google.com> [Thu, 14 Jun 2018 11:49:10 -0400] rev 38323
tests: suppress read(-1) -> '' calls in fileobjectobserver This stabilizes the test output of the low-level wireproto tests between Python 2 and 3. I don't feel great about this change, but otherwise we get a ton of extra read(-1) output on Python 3, and this feels like a more sustainable solution. Bonus: test-ssh-proto-unbundle.t now passes on Python 3. Differential Revision: https://phab.mercurial-scm.org/D3733
(0) -30000 -10000 -3000 -1000 -300 -100 -10 +10 +100 +300 +1000 +3000 +10000 tip