Thu, 17 Jan 2019 09:17:12 -0800 cleanup: delete lots of unused local variables
Martin von Zweigbergk <martinvonz@google.com> [Thu, 17 Jan 2019 09:17:12 -0800] rev 41365
cleanup: delete lots of unused local variables These were found by IntelliJ. There are many more, but these seemed pretty safe. Differential Revision: https://phab.mercurial-scm.org/D5629
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
(0) -30000 -10000 -3000 -1000 -300 -100 -10 +10 +100 +300 +1000 +3000 +10000 tip