Mon, 24 Sep 2018 14:46:37 -0700 localrepo: use context manager for lock and transaction in commitctx()
Martin von Zweigbergk <martinvonz@google.com> [Mon, 24 Sep 2018 14:46:37 -0700] rev 41364
localrepo: use context manager for lock and transaction in commitctx() Differential Revision: https://phab.mercurial-scm.org/D5624
Wed, 16 Jan 2019 17:34:59 -0800 localrepo: use context manager for locks in commit()
Martin von Zweigbergk <martinvonz@google.com> [Wed, 16 Jan 2019 17:34:59 -0800] rev 41363
localrepo: use context manager for locks in commit() Differential Revision: https://phab.mercurial-scm.org/D5623
Wed, 16 Jan 2019 17:33:47 -0800 localrepo: use context manager for transaction in commit()
Martin von Zweigbergk <martinvonz@google.com> [Wed, 16 Jan 2019 17:33:47 -0800] rev 41362
localrepo: use context manager for transaction in commit() A side-effect is that the transaction is released a little earlier, so the "commit message saved in ..." messages now comes after the "rollback completed" message. That seems slightly better to me. Differential Revision: https://phab.mercurial-scm.org/D5622
Wed, 16 Jan 2019 17:46:39 -0800 commit: print "commit message saved in" message also if bookmark update fails
Martin von Zweigbergk <martinvonz@google.com> [Wed, 16 Jan 2019 17:46:39 -0800] rev 41361
commit: print "commit message saved in" message also if bookmark update fails The bookmark update is done within the same transaction, so if fails, the commit will also be rolled back. I just happened to notice this while messing with this code; we have not had reports of crashing bookmark updates from our users. The same applies to the clearing of the merge state, although I don't think that's currently tied into the transaction. Differential Revision: https://phab.mercurial-scm.org/D5621
Thu, 17 Jan 2019 22:07:58 -0800 remotefilelog: remove pointless return statement from constructor
Martin von Zweigbergk <martinvonz@google.com> [Thu, 17 Jan 2019 22:07:58 -0800] rev 41360
remotefilelog: remove pointless return statement from constructor Differential Revision: https://phab.mercurial-scm.org/D5630
Tue, 15 Jan 2019 22:57:09 +0800 revset: support ranges in #generations relation
Anton Shestakov <av6@dwimlabs.net> [Tue, 15 Jan 2019 22:57:09 +0800] rev 41359
revset: support ranges in #generations relation
Thu, 24 Jan 2019 18:14:39 +0300 tests: fix module-import warnings in test-update-atomic.t
Pulkit Goyal <pulkit@yandex-team.ru> [Thu, 24 Jan 2019 18:14:39 +0300] rev 41358
tests: fix module-import warnings in test-update-atomic.t These were caught by test-check-module-imports.t on Python 3. This should also make python3-buildbot green again. Differential Revision: https://phab.mercurial-scm.org/D5674
Fri, 18 Jan 2019 19:28:31 +0530 py3: use dict.items() instead of dict.iteritems() in tests/test-lfs-server.t
Pulkit Goyal <pulkit@yandex-team.ru> [Fri, 18 Jan 2019 19:28:31 +0530] rev 41357
py3: use dict.items() instead of dict.iteritems() in tests/test-lfs-server.t dict.iteritems() is not present on Python 3. Differential Revision: https://phab.mercurial-scm.org/D5673
Fri, 18 Jan 2019 19:26:28 +0530 py3: add b'' prefixes in tests/test-lfs-serve.t
Pulkit Goyal <pulkit@yandex-team.ru> [Fri, 18 Jan 2019 19:26:28 +0530] rev 41356
py3: add b'' prefixes in tests/test-lfs-serve.t # skip-blame because just b'' prefixes Differential Revision: https://phab.mercurial-scm.org/D5672
Thu, 24 Jan 2019 18:09:34 +0300 py3: add b'' prefixes in doc/check-seclevel.py
Pulkit Goyal <pulkit@yandex-team.ru> [Thu, 24 Jan 2019 18:09:34 +0300] rev 41355
py3: add b'' prefixes in doc/check-seclevel.py # skip-blame because just b'' prefixes Differential Revision: https://phab.mercurial-scm.org/D5670
Thu, 24 Jan 2019 15:52:59 -0500 tests: remove some over-globbing in test-dispatch.t
Augie Fackler <augie@google.com> [Thu, 24 Jan 2019 15:52:59 -0500] rev 41354
tests: remove some over-globbing in test-dispatch.t Hilariously, this was exposed by Python 3 work. Differential Revision: https://phab.mercurial-scm.org/D5689
Thu, 24 Jan 2019 15:23:20 -0500 py3: port test-parseindex.t to Python 3
Augie Fackler <augie@google.com> [Thu, 24 Jan 2019 15:23:20 -0500] rev 41353
py3: port test-parseindex.t to Python 3 Differential Revision: https://phab.mercurial-scm.org/D5686
Thu, 24 Jan 2019 15:04:30 -0500 py3: almost fix test-trusted.py
Augie Fackler <augie@google.com> [Thu, 24 Jan 2019 15:04:30 -0500] rev 41352
py3: almost fix test-trusted.py The test now only fails due to output format changes on the repr of mercurial.error.ParseError. I'm not really sure how to approach that for now. Differential Revision: https://phab.mercurial-scm.org/D5685
Fri, 25 Jan 2019 18:55:23 +0900 merge with stable
Yuya Nishihara <yuya@tcha.org> [Fri, 25 Jan 2019 18:55:23 +0900] rev 41351
merge with stable
Wed, 23 Jan 2019 07:49:36 -0500 rust-cpython: raising error.WdirUnsupported stable
Georges Racinet <georges.racinet@octobus.net> [Wed, 23 Jan 2019 07:49:36 -0500] rev 41350
rust-cpython: raising error.WdirUnsupported The Graph implementation of hg-cpython returns the appropriate error upon encounter with the working directory special revision number, and this gives us in particular a code path to test from test-rust-ancestors.py In the current implementation, the exception is actually raised from the iterator instantiation; we are nonetheless consuming the iterator in the test with `list()` in order not to depend on implementation details.
Wed, 23 Jan 2019 07:47:04 -0500 rust: error for WdirUnsupported with cpython conversion as exception stable
Georges Racinet <georges.racinet@octobus.net> [Wed, 23 Jan 2019 07:47:04 -0500] rev 41349
rust: error for WdirUnsupported with cpython conversion as exception This introduces WorkingDirectoryUnsupported as an enum variant of GraphError in the core and converts it to the expected `mercurial.error.WdirUnsupported`.
(0) -30000 -10000 -3000 -1000 -300 -100 -16 +16 +100 +300 +1000 +3000 +10000 tip