Fri, 04 Dec 2015 17:41:02 +0000 perf: improve grammar of gettimer comment
timeless <timeless@mozdev.org> [Fri, 04 Dec 2015 17:41:02 +0000] rev 27303
perf: improve grammar of gettimer comment
Sun, 06 Dec 2015 22:20:08 -0800 tests: use absolute_import in tinyproxy
Gregory Szorc <gregory.szorc@gmail.com> [Sun, 06 Dec 2015 22:20:08 -0800] rev 27302
tests: use absolute_import in tinyproxy Thus begins a series of adding absolute_import to a bunch of files for Python 3 compatibility.
Sun, 06 Dec 2015 22:02:39 -0800 tests: use absolulte_import in test-wireproto.py
Gregory Szorc <gregory.szorc@gmail.com> [Sun, 06 Dec 2015 22:02:39 -0800] rev 27301
tests: use absolulte_import in test-wireproto.py
Sun, 06 Dec 2015 22:05:19 -0800 tests: use absolute_import in test-walkrepo
Gregory Szorc <gregory.szorc@gmail.com> [Sun, 06 Dec 2015 22:05:19 -0800] rev 27300
tests: use absolute_import in test-walkrepo
Sun, 06 Dec 2015 22:27:53 -0800 tests: use absolute_import in hgweberror.py
Gregory Szorc <gregory.szorc@gmail.com> [Sun, 06 Dec 2015 22:27:53 -0800] rev 27299
tests: use absolute_import in hgweberror.py
Sun, 06 Dec 2015 22:27:18 -0800 tests: use absolute_import in hghave.py
Gregory Szorc <gregory.szorc@gmail.com> [Sun, 06 Dec 2015 22:27:18 -0800] rev 27298
tests: use absolute_import in hghave.py
Sun, 06 Dec 2015 22:26:12 -0800 tests: use absolute_import for heredoctest.py
Gregory Szorc <gregory.szorc@gmail.com> [Sun, 06 Dec 2015 22:26:12 -0800] rev 27297
tests: use absolute_import for heredoctest.py
Sun, 06 Dec 2015 22:25:41 -0800 tests: use absolute_import in /get-with-headers.py
Gregory Szorc <gregory.szorc@gmail.com> [Sun, 06 Dec 2015 22:25:41 -0800] rev 27296
tests: use absolute_import in /get-with-headers.py While I was here, I removed condition code for failure to import json. This code was necessary to support Python < 2.6, which didn't include the json module.
Sun, 06 Dec 2015 22:23:37 -0800 tests: use absolute_import in generate-working-copy-states.py
Gregory Szorc <gregory.szorc@gmail.com> [Sun, 06 Dec 2015 22:23:37 -0800] rev 27295
tests: use absolute_import in generate-working-copy-states.py
Fri, 13 Nov 2015 14:35:36 +0800 hgweb: move entry-preparing code from webcommands to webutils.commonentry()
Anton Shestakov <av6@dwimlabs.net> [Fri, 13 Nov 2015 14:35:36 +0800] rev 27294
hgweb: move entry-preparing code from webcommands to webutils.commonentry() The new function is used to fill basic information about a ctx, such as revision number and hash, author, commit message, etc. Before, every webcommand used to get this basic information on its own using some boilerplate code, and some things in some places just weren't available.
Mon, 30 Nov 2015 19:30:16 +0000 grammar: favor zero, one, two over ... or no
timeless <timeless@mozdev.org> [Mon, 30 Nov 2015 19:30:16 +0000] rev 27293
grammar: favor zero, one, two over ... or no
Mon, 30 Nov 2015 19:29:46 +0000 commands: use Oxford comma (help clone)
timeless <timeless@mozdev.org> [Mon, 30 Nov 2015 19:29:46 +0000] rev 27292
commands: use Oxford comma (help clone)
Wed, 09 Dec 2015 08:28:53 +0900 commit: make commit acquire store lock before processing for consistency
FUJIWARA Katsunori <foozy@lares.dti.ne.jp> [Wed, 09 Dec 2015 08:28:53 +0900] rev 27291
commit: make commit acquire store lock before processing for consistency If acquisition of wlock waits for another "hg commit" process to release it, dirstate will refer newly committed revision after acquisition of wlock. At that time, '00changelog.i' on the filesystem contains this new revision, but in-memory 'repo.changelog' doesn't, if it is cached without store lock (slock) before updating by another "hg commit". This makes validating parents at re-loading 'repo.dirstate' from '.hg/dirstate' replace such new revision with 'nullid'. Then, 'localrepository.commit()' creates "orphan" revision (see issue4368 for detail). a01d3d32b53a makes 'commands.commit()' acquire both wlock and slock before processing to avoid this issue at "hg commit". But similar issue can occur even after a01d3d32b53a, if 3rd party extension does: - refer 'repo.changelog' outside wlock scope, and - invoke 'repo.commit()' directly (instead of 'commands.commit()') This patch makes 'commit()' acquire slock before processing, to refer recent changelog at validating parents of 'repo.dirstate'.
Wed, 09 Dec 2015 08:28:53 +0900 censor: make censor acquire locks before processing
FUJIWARA Katsunori <foozy@lares.dti.ne.jp> [Wed, 09 Dec 2015 08:28:53 +0900] rev 27290
censor: make censor acquire locks before processing Before this patch, "hg censor" executes below: - without acquisition of wlock, examine whether the working directory refers the revision of the file to be censored or not - without acquisition of store lock (slock), replace existing filelog of file to be censored with censored one, Replacement consists of steps below, and it is assumed that the destination filelog at (1) isn't changed before renaming at (3). 1. read existing filelog in 2. write filelog entries (both censored and not) into temporary file 3. rename from temporary file to existing filelog to be censored It may cause unintentional result, if another command runs parallelly (see also issue4368). This patch makes "hg censor" acquire wlock and slock before processing.
Wed, 09 Dec 2015 08:28:53 +0900 transplant: widen wlock scope of transplant for consitency while processing
FUJIWARA Katsunori <foozy@lares.dti.ne.jp> [Wed, 09 Dec 2015 08:28:53 +0900] rev 27289
transplant: widen wlock scope of transplant for consitency while processing Before this patch, "hg transplant" executes below before acquisition of wlock. - cmdutil.checkunfinished() - repo.status() for dirty check - repo.dirstate.parents() It may cause unintentional result, if another command runs parallelly (see also issue4368). This patch makes "hg transplant" acquire wlock before processing instead of acquiring wlock in each of 'transplanter.apply()' and 'transplanter.recover()'.
Wed, 09 Dec 2015 08:28:53 +0900 shelve: remove redundant acquisition of wlock for sub commands of unshelve
FUJIWARA Katsunori <foozy@lares.dti.ne.jp> [Wed, 09 Dec 2015 08:28:53 +0900] rev 27288
shelve: remove redundant acquisition of wlock for sub commands of unshelve Previous patch ensures that wlock is acquired before processing for "hg unshelve". It makes acquisition of wlock in each functions below redundant. - unshelveabort() for "unshelve --abort" - unshelvecontinue() for "unshelve --continue"
Wed, 09 Dec 2015 08:28:53 +0900 shelve: widen wlock scope of unshelve for consistency while processing
FUJIWARA Katsunori <foozy@lares.dti.ne.jp> [Wed, 09 Dec 2015 08:28:53 +0900] rev 27287
shelve: widen wlock scope of unshelve for consistency while processing Before this patch, "hg unshelve" of shelve extension executes below before acquisition of wlock: - cmdutil.checkunfinished() - examine existence of (specified) shelve file It may cause unintentional result, if another command runs parallelly (see also issue4368). This patch widens wlock scope of "hg unshelve" of shelve extension for consistency while processing.
Sun, 06 Dec 2015 17:07:50 -0800 perf: add perflrucachedict command
Gregory Szorc <gregory.szorc@gmail.com> [Sun, 06 Dec 2015 17:07:50 -0800] rev 27286
perf: add perflrucachedict command It measures time to construct, perform gets, sets, or mixed mode operations on a cache of configurable size with variable numbers of operations.
Sun, 06 Dec 2015 22:22:09 -0800 tests/filterpyflakes: use absolute_import
Gregory Szorc <gregory.szorc@gmail.com> [Sun, 06 Dec 2015 22:22:09 -0800] rev 27285
tests/filterpyflakes: use absolute_import
Sun, 06 Dec 2015 22:14:39 -0800 tests/fakepatchtime.py: use absolute_import
Gregory Szorc <gregory.szorc@gmail.com> [Sun, 06 Dec 2015 22:14:39 -0800] rev 27284
tests/fakepatchtime.py: use absolute_import
Sun, 06 Dec 2015 22:13:36 -0800 tests/fakedirstatewritetime.py: use absolute_import
Gregory Szorc <gregory.szorc@gmail.com> [Sun, 06 Dec 2015 22:13:36 -0800] rev 27283
tests/fakedirstatewritetime.py: use absolute_import
Sun, 06 Dec 2015 22:12:07 -0800 tests/dumbhttp: use absolute_import
Gregory Szorc <gregory.szorc@gmail.com> [Sun, 06 Dec 2015 22:12:07 -0800] rev 27282
tests/dumbhttp: use absolute_import
Sun, 06 Dec 2015 22:10:10 -0800 tests/autodiff.py: use absolute_import
Gregory Szorc <gregory.szorc@gmail.com> [Sun, 06 Dec 2015 22:10:10 -0800] rev 27281
tests/autodiff.py: use absolute_import
Sun, 06 Dec 2015 22:07:13 -0800 tests/test-ancestor: use absolute_import
Gregory Szorc <gregory.szorc@gmail.com> [Sun, 06 Dec 2015 22:07:13 -0800] rev 27280
tests/test-ancestor: use absolute_import
Sun, 06 Dec 2015 22:39:12 -0800 tests: add test for Python 3 compatibility
Gregory Szorc <gregory.szorc@gmail.com> [Sun, 06 Dec 2015 22:39:12 -0800] rev 27279
tests: add test for Python 3 compatibility Python 3 is inevitable. There have been incremental movements towards converting the code base to be Python 3 compatible. Unfortunately, we don't have any tests that look for Python 3 compatibility. This patch changes that. We introduce a check-py3-compat.py script whose role is to verify Python 3 compatibility of the files passed in. We add a test that calls this script with all .py files from the source checkout. The script currently only verifies that absolute_import and print_function are used. These are the low hanging fruits for Python compatbility. Over time, we can include more checks, including verifying we're able to load each Python file with Python 3. You have to start somewhere. Accepting this patch means that all new .py files must have absolute_import and print_function (if "print" is used) to avoid a new warning about Python 3 incompatibility. We've already converted several files to use absolute_import and print_function is in the same boat, so I don't think this is such a radical proposition.
Mon, 07 Dec 2015 18:06:13 -0600 merge with stable
Matt Mackall <mpm@selenic.com> [Mon, 07 Dec 2015 18:06:13 -0600] rev 27278
merge with stable
Sat, 05 Dec 2015 23:14:49 -0800 localrepo: reinstate localrepo.parents with a deprecation warning
Pierre-Yves David <pierre-yves.david@fb.com> [Sat, 05 Dec 2015 23:14:49 -0800] rev 27277
localrepo: reinstate localrepo.parents with a deprecation warning The function was dropped in 3fe8cb40c9c5. This API drop brokes three of my extensions including some critical to my workflow like tortoisehg. Lets mark this API for death and give people time to fix their code.
Sat, 05 Dec 2015 23:34:07 -0800 bookmark: deprecate 'bmstore.write' method
Pierre-Yves David <pierre-yves.david@fb.com> [Sat, 05 Dec 2015 23:34:07 -0800] rev 27276
bookmark: deprecate 'bmstore.write' method This function does not collaborate with the transaction and must disappear. As we have likely a lot of third party users, we make it deprecated to let them some time to upgrade their code. Thanks goes to Laurent Charignon for cleanup the last remains of the 'write' method.
Sat, 05 Dec 2015 23:05:49 -0800 ui: add a 'deprecwarn' helper to issue deprecation warnings
Pierre-Yves David <pierre-yves.david@fb.com> [Sat, 05 Dec 2015 23:05:49 -0800] rev 27275
ui: add a 'deprecwarn' helper to issue deprecation warnings As discussed on the list, we are adding an official way to keep old API around for a short time in order to help third party developer to catch up. The deprecated API will issue developer warning (issued by default during test runs) to warn extensions authors that they need to upgrade their code without instantaneously breaking tool chains and normal users. The version is passed as an explicit argument so that developer think about it and a potential future script can automatically check for it. This is not build as a decorator because accessing the 'ui' instance will likely be different each time. The message is also free form because deprecated API are replaced in a variety of ways. I'm not super happy about the final rendering of that message, but this is a developer oriented warning and I would like to move forward.
Sat, 05 Dec 2015 23:05:33 -0800 ui: add a 'stacklevel' argument to 'develwarn'
Pierre-Yves David <pierre-yves.david@fb.com> [Sat, 05 Dec 2015 23:05:33 -0800] rev 27274
ui: add a 'stacklevel' argument to 'develwarn' This allows helper functions (like deprecation warning) to prepare a devel warning for higher up in the stack. The argument is named after the one in the Python's 'warning,warn' function.
Sun, 06 Dec 2015 14:28:35 +0900 import-checker: tell which symbol causes "direct symbol import"
Yuya Nishihara <yuya@tcha.org> [Sun, 06 Dec 2015 14:28:35 +0900] rev 27273
import-checker: tell which symbol causes "direct symbol import" This would be sometimes useful to understand why import-checker.py complains about it.
Sun, 06 Dec 2015 14:18:19 +0900 import-checker: allow absolute imports of sub modules from local packages
Yuya Nishihara <yuya@tcha.org> [Sun, 06 Dec 2015 14:18:19 +0900] rev 27272
import-checker: allow absolute imports of sub modules from local packages Before this patch, import-checker.py didn't know if a name in ImportFrom statement are module or not. Therefore, it complained the following example did "direct symbol import from mercurial". # hgext/foo.py from mercurial import hg This patch reuses the dict of local modules to filter out sub-module names.
(0) -10000 -3000 -1000 -300 -100 -50 -32 +32 +50 +100 +300 +1000 +3000 +10000 tip