Fri, 15 May 2015 02:07:43 +0800 hgweb: split some long lines in paper, gitweb and monoblue styles
Anton Shestakov <engored@ya.ru> [Fri, 15 May 2015 02:07:43 +0800] rev 25108
hgweb: split some long lines in paper, gitweb and monoblue styles This will ease future patches for the templates. As a result of this patch, paper style has one visual change in log/shortlog/file log view: the spacing between commit message and the first tag (or branch name, or bookmark) is now roughly who spaces wide instead of one space wide. This spacing is consistent with the one between branch names/tags/bookmarks themselves, so it looks better. In gitweb style, the change from non-breakable space to regular space is consistent with other elements. In monoblue the change is not noticeable.
Wed, 13 May 2015 11:22:06 -0700 run-tests: add a --profile-runner option
Augie Fackler <augie@google.com> [Wed, 13 May 2015 11:22:06 -0700] rev 25107
run-tests: add a --profile-runner option While in the throes of a recent run-tests adventure, I found it useful to have profiler output for the testrunner itself. Adding it was simple enough and seems worth keeping around.
Fri, 15 May 2015 10:24:59 +0200 test-http: drop compatibility check on Python >= 2.4.3
Gilles Moris <gilles.moris@free.fr> [Fri, 15 May 2015 10:24:59 +0200] rev 25106
test-http: drop compatibility check on Python >= 2.4.3 This is obsolete now that Python < 2.6 is no more supported. This is thus a backout of c499fff76440.
Fri, 15 May 2015 22:38:24 +0900 revset: remove unused 'only' from methods table
Yuya Nishihara <yuya@tcha.org> [Fri, 15 May 2015 22:38:24 +0900] rev 25105
revset: remove unused 'only' from methods table The infix 'only' operator is mapped to 'only()' function by optimize(), so it won't be looked up as a method. The test shows it.
Tue, 14 Apr 2015 16:23:54 -0400 shelve: allow --patch and --stat without --list for a single shelf
Tony Tung <tonytung@fb.com> [Tue, 14 Apr 2015 16:23:54 -0400] rev 25104
shelve: allow --patch and --stat without --list for a single shelf It's annoying having to specify --list and --patch/--stat when all you really want to do is to dump a patch. This creates an explicit --patch/--stat command that is executed if --list is not specified. It ensures that 1) there is only one shelf name specified and 2) that the shelf exists. Then it redirects to the original listcmd code.
Tue, 14 Apr 2015 16:23:07 -0400 shelve: refactor allowables to specify sets of valid operations
Tony Tung <tonytung@fb.com> [Tue, 14 Apr 2015 16:23:07 -0400] rev 25103
shelve: refactor allowables to specify sets of valid operations This will allow us to have --patch and --stat as standalone operations that don't require --list, as well as pairing them with --list.
Fri, 15 May 2015 11:52:09 -0500 merge with stable
Matt Mackall <mpm@selenic.com> [Fri, 15 May 2015 11:52:09 -0500] rev 25102
merge with stable
Thu, 14 May 2015 21:35:06 -0700 rebase: check that the bookmark is still valid when restoring (issue4669) stable
Tony Tung <tonytung@fb.com> [Thu, 14 May 2015 21:35:06 -0700] rev 25101
rebase: check that the bookmark is still valid when restoring (issue4669) After a rebase --abort, we attempt to restore the previously active bookmark. We need to ensure that the bookmark still exists.
Tue, 14 Apr 2015 12:53:48 -0700 bookmarks: rename current to active in variables and comments
Ryan McElroy <rmcelroy@fb.com> [Tue, 14 Apr 2015 12:53:48 -0700] rev 25100
bookmarks: rename current to active in variables and comments Today, the terms 'active' and 'current' are interchangeably used throughout the codebase in reference to the active bookmark (the bookmark that will be updated with the next commit). This leads to confusion among developers and users. This patch is part of a series to standardize the usage to 'active' throughout the mercurial codebase and user interface.
Thu, 14 May 2015 21:34:46 -0700 rebase: remove extraneous blank at the end of file
Tony Tung <tonytung@fb.com> [Thu, 14 May 2015 21:34:46 -0700] rev 25099
rebase: remove extraneous blank at the end of file
Thu, 07 May 2015 23:40:29 -0700 run-tests: include 'start' and 'end' in --time output
Pierre-Yves David <pierre-yves.david@fb.com> [Thu, 07 May 2015 23:40:29 -0700] rev 25098
run-tests: include 'start' and 'end' in --time output This is useful information to understand what is taking time in tests. Both are included because I can see myself sorting this output using shell script. Having both data makes it much easier than extracting 'start'+'real'.
Thu, 07 May 2015 23:34:58 -0700 run-tests: track start and end time of tests
Pierre-Yves David <pierre-yves.david@fb.com> [Thu, 07 May 2015 23:34:58 -0700] rev 25097
run-tests: track start and end time of tests We currently have information about how long each test took, but we have no data about their actual scheduling. So we now track when a test started and stopped (in the referential of the whole tests run) to expose this information. The data is currently in the json only because the json output is meant to be extensible. Later changeset will includes this data in the text output and we will be happy to bikeshed its formating there. Yes, "end" is actually just "start" + "time", but computing it an including it in the output is simple, cheap and convenient.
Fri, 15 May 2015 09:07:27 -0400 templater: look for mapfiles in template paths
Jordi Gutiérrez Hermoso <jordigh@octave.org> [Fri, 15 May 2015 09:07:27 -0400] rev 25096
templater: look for mapfiles in template paths This will allow %include statements to search the default template paths in addition to the directory where the %including file is.
Fri, 15 May 2015 09:04:32 -0400 config: give it an includepaths option for looking for config files
Jordi Gutiérrez Hermoso <jordigh@octave.org> [Fri, 15 May 2015 09:04:32 -0400] rev 25095
config: give it an includepaths option for looking for config files It is desirable to "derive" templates from the provided templates. A simple way to do this is e.g. %include map-cmdline.default in your own mapfile. Then you only have to redefine a few templates instead of copying over the whole thing. This %include mechanism already works for the built-in templates because by default it *only* looks for files that are in the same directory as the including mapfile. With this changeset, config grows an option to add more include paths for config files.
Fri, 15 May 2015 22:32:31 +0900 revset: map postfix '%' to only() to optimize operand recursively (issue4670) stable
Yuya Nishihara <yuya@tcha.org> [Fri, 15 May 2015 22:32:31 +0900] rev 25094
revset: map postfix '%' to only() to optimize operand recursively (issue4670) Instead of keeping 'onlypost' as a method, this patch rewrites it to 'only' function. This way, 'x%' always has the same weight as 'only(x)'.
Fri, 08 May 2015 14:13:12 -0700 dirs.c: pass C string, not Python string, to _finddir()
Martin von Zweigbergk <martinvonz@google.com> [Fri, 08 May 2015 14:13:12 -0700] rev 25093
dirs.c: pass C string, not Python string, to _finddir() The callers already have the C string, and although the PyString_AS_STRING() macro is probably free, this simplifies the code.
Fri, 08 May 2015 14:11:00 -0700 dirs.c: extract 'cpath' variable in _delpath() to match _addpath()
Martin von Zweigbergk <martinvonz@google.com> [Fri, 08 May 2015 14:11:00 -0700] rev 25092
dirs.c: extract 'cpath' variable in _delpath() to match _addpath() The PyString_AS_STRING() macro is probably free, but this makes _delpath() more similar to _addpath() and simplifies the next patch.
Mon, 13 Apr 2015 23:21:02 -0700 treemanifest: store submanifest revlog per directory
Martin von Zweigbergk <martinvonz@google.com> [Mon, 13 Apr 2015 23:21:02 -0700] rev 25091
treemanifest: store submanifest revlog per directory With this change, when tree manifests are enabled (in .hg/requires), commits will be written with one manifest revlog per directory. The manifest revlogs are stored in .hg/store/meta/$dir/00manifest.[id]. Flat manifests can still be read and interacted with as usual (they are also read into treemanifest instances). The functionality for writing treemanifest as a flat manifest to disk is still left in the code; tests still pass with '_treeinmem=True' hardcoded. Exchange is not yet implemented.
Fri, 15 May 2015 10:29:39 -0500 hghave: use try/except/finally
Matt Mackall <mpm@selenic.com> [Fri, 15 May 2015 10:29:39 -0500] rev 25090
hghave: use try/except/finally
Fri, 15 May 2015 10:00:46 -0500 setup: use try/except/finally
Matt Mackall <mpm@selenic.com> [Fri, 15 May 2015 10:00:46 -0500] rev 25089
setup: use try/except/finally This will raise a syntax error for people who attempt to use Py2.4, but that's already going to fail and we have no way to keep other 2.6isms from creeping in since we've removed the check-code rules and the buildbot.
Fri, 15 May 2015 09:58:21 -0500 util: use try/except/finally
Matt Mackall <mpm@selenic.com> [Fri, 15 May 2015 09:58:21 -0500] rev 25088
util: use try/except/finally
Fri, 15 May 2015 09:58:02 -0500 tags: use try/except/finally
Matt Mackall <mpm@selenic.com> [Fri, 15 May 2015 09:58:02 -0500] rev 25087
tags: use try/except/finally
Fri, 15 May 2015 09:57:44 -0500 repoview: use try/except/finally
Matt Mackall <mpm@selenic.com> [Fri, 15 May 2015 09:57:44 -0500] rev 25086
repoview: use try/except/finally
Fri, 15 May 2015 09:57:02 -0500 httppeer: use try/except/finally
Matt Mackall <mpm@selenic.com> [Fri, 15 May 2015 09:57:02 -0500] rev 25085
httppeer: use try/except/finally
Fri, 15 May 2015 09:56:43 -0500 hooks: use try/except/finally
Matt Mackall <mpm@selenic.com> [Fri, 15 May 2015 09:56:43 -0500] rev 25084
hooks: use try/except/finally
Fri, 15 May 2015 09:56:27 -0500 hgweb: use try/except/finally
Matt Mackall <mpm@selenic.com> [Fri, 15 May 2015 09:56:27 -0500] rev 25083
hgweb: use try/except/finally
Fri, 15 May 2015 09:56:05 -0500 commands: use try/except/finally
Matt Mackall <mpm@selenic.com> [Fri, 15 May 2015 09:56:05 -0500] rev 25082
commands: use try/except/finally
Fri, 15 May 2015 09:55:47 -0500 bookmarks: use try/except/finally
Matt Mackall <mpm@selenic.com> [Fri, 15 May 2015 09:55:47 -0500] rev 25081
bookmarks: use try/except/finally
Fri, 15 May 2015 09:55:31 -0500 shelve: use try/except/finally
Matt Mackall <mpm@selenic.com> [Fri, 15 May 2015 09:55:31 -0500] rev 25080
shelve: use try/except/finally
Fri, 15 May 2015 09:55:15 -0500 largefiles: use try/except/finally
Matt Mackall <mpm@selenic.com> [Fri, 15 May 2015 09:55:15 -0500] rev 25079
largefiles: use try/except/finally
Fri, 15 May 2015 09:54:56 -0500 factotum: use try/except/finally
Matt Mackall <mpm@selenic.com> [Fri, 15 May 2015 09:54:56 -0500] rev 25078
factotum: use try/except/finally
Fri, 15 May 2015 09:54:35 -0500 check-code: drop try/except/finally check
Matt Mackall <mpm@selenic.com> [Fri, 15 May 2015 09:54:35 -0500] rev 25077
check-code: drop try/except/finally check
Thu, 14 May 2015 09:04:48 +0200 util.h: kill no longer needed definitions for Python < 2.6
Adrian Buehlmann <adrian@cadifra.com> [Thu, 14 May 2015 09:04:48 +0200] rev 25076
util.h: kill no longer needed definitions for Python < 2.6 see e1fb276d4619
Thu, 14 May 2015 16:28:28 -0500 merge with stable
Matt Mackall <mpm@selenic.com> [Thu, 14 May 2015 16:28:28 -0500] rev 25075
merge with stable
Thu, 14 May 2015 11:04:36 +0200 setup: integrate osutil C extension into extmodules initialization
Adrian Buehlmann <adrian@cadifra.com> [Thu, 14 May 2015 11:04:36 +0200] rev 25074
setup: integrate osutil C extension into extmodules initialization
Thu, 14 May 2015 11:04:35 +0200 setup: move osutil_ldflags logic to before extmodules definition
Adrian Buehlmann <adrian@cadifra.com> [Thu, 14 May 2015 11:04:35 +0200] rev 25073
setup: move osutil_ldflags logic to before extmodules definition
Thu, 14 May 2015 11:04:31 +0200 setup: kill pure hack for osutil on Windows for Python 2.4
Adrian Buehlmann <adrian@cadifra.com> [Thu, 14 May 2015 11:04:31 +0200] rev 25072
setup: kill pure hack for osutil on Windows for Python 2.4 see e1fb276d4619
Thu, 14 May 2015 11:37:36 +0200 windows: add comment in normcase()
Adrian Buehlmann <adrian@cadifra.com> [Thu, 14 May 2015 11:37:36 +0200] rev 25071
windows: add comment in normcase() see also 3c5e818ac679
Sun, 10 May 2015 10:57:24 -0400 rebase: clear merge when aborting before any rebasing (issue4661) stable
Jordi Gutiérrez Hermoso <jordigh@octave.org> [Sun, 10 May 2015 10:57:24 -0400] rev 25070
rebase: clear merge when aborting before any rebasing (issue4661) The check of the inrebase function was not correct, and it failed to consider the situation in which nothing has been rebased yet, *and* the working dir had been updated away from the initial revision. But this is easy to fix. Given the rebase state, we know exactly where we should be standing: on the first unrebased commit. We check that instead. I also took the liberty to rename the function, as "inrebase" doesn't really describe the situation: we could still be in a rebase state yet the user somehow forcibly updated to a different revision. We also check that we're in a merge state, since an interrupted merge is the only "safe" way to interrupt a rebase. If the rebase got interrupted by power loss or whatever (so there's no merge state), it's still safer to not blow away the working directory.
Sun, 10 May 2015 10:02:15 -0400 test-rebase-abort: add test from issue4009 stable
Jordi Gutiérrez Hermoso <jordigh@octave.org> [Sun, 10 May 2015 10:02:15 -0400] rev 25069
test-rebase-abort: add test from issue4009 The fix for issue4009, namely fe78eb7bcca0, introduced issue4661. Let's make sure that the fix for issue4661 will not reintroduce issue4009.
Fri, 08 May 2015 15:00:07 -0700 run-test.py: greatly increase the priority of 'check-code' tests
Pierre-Yves David <pierre-yves.david@fb.com> [Fri, 08 May 2015 15:00:07 -0700] rev 25068
run-test.py: greatly increase the priority of 'check-code' tests As check-code is actually quite long to run for its file size, this prevent them to be scheduled too late during the test run. This reduces my typical test run from 107 seconds to 90 seconds
Fri, 08 May 2015 00:04:07 -0700 run-tests: allow different extra weight for slow tests
Pierre-Yves David <pierre-yves.david@fb.com> [Fri, 08 May 2015 00:04:07 -0700] rev 25067
run-tests: allow different extra weight for slow tests The 'test-check-code-hg.t' file is not big enough to be prioritized properly. As a result my tests run often spend about 15 seconds running only it at the end of its tests run. We make the "slow" mechanism a bit smarter to adjust the extra weight of each category independently in a future patch.
Thu, 07 May 2015 21:00:46 -0700 ignore: refactor syntax concatenation
Durham Goode <durham@fb.com> [Thu, 07 May 2015 21:00:46 -0700] rev 25066
ignore: refactor syntax concatenation This refactors the syntax+rule concatenation logic to be more separated. It determines the syntax and the rule separately and then puts them back together. This will help in a later patch when we want to process just the rule before it gets concatenated.
Thu, 07 May 2015 20:57:37 -0700 ignore: refactor file read into a function
Durham Goode <durham@fb.com> [Thu, 07 May 2015 20:57:37 -0700] rev 25065
ignore: refactor file read into a function This refactors the ignore file reading code into a function so that in a future patch we can make it recursive.
Thu, 14 May 2015 01:49:10 +0900 import-checker: loop to get list of locally defined modules at first
FUJIWARA Katsunori <foozy@lares.dti.ne.jp> [Thu, 14 May 2015 01:49:10 +0900] rev 25064
import-checker: loop to get list of locally defined modules at first This is a preparation for subsequent patches, which expect that all locally defined (= mercurial specific) modules are already known before examinations. Looping twice for specified modules is a little redundant, but reasonable cost for improvement in subsequent patches.
Thu, 14 May 2015 01:49:10 +0900 import-checker: add xargs like mode
FUJIWARA Katsunori <foozy@lares.dti.ne.jp> [Thu, 14 May 2015 01:49:10 +0900] rev 25063
import-checker: add xargs like mode Before this patch, "import-check.py" is invoked via "xargs" in "test-module-imports.t", but it doesn't ensure that "import-checker.py" is certainly invoked with all mercurial specific files at once. "xargs" may invoke specified command multiple times with part of arguments given from stdin: according to "xargs(1)" man page, this dividing arguments is system-dependent. This patch adds "xargs" like mode to "import-checker.py". This can ensure that "import-checker.py" is certainly invoked with all mercurial specific files at once in "test-module-imports.t". This is assumed by subsequent patches.
Wed, 13 May 2015 20:36:56 +0200 store: add comment in _hashencode with reason for skipping the first 5 chars
Adrian Buehlmann <adrian@cadifra.com> [Wed, 13 May 2015 20:36:56 +0200] rev 25062
store: add comment in _hashencode with reason for skipping the first 5 chars
Tue, 14 Apr 2015 10:57:15 -0400 test-run-tests: fix for Python 3.5
Augie Fackler <augie@google.com> [Tue, 14 Apr 2015 10:57:15 -0400] rev 25061
test-run-tests: fix for Python 3.5 This test now passes in both 3.5 and 2.6.
Tue, 14 Apr 2015 16:09:39 -0400 run-tests: make sure all script lines are bytes
Augie Fackler <augie@google.com> [Tue, 14 Apr 2015 16:09:39 -0400] rev 25060
run-tests: make sure all script lines are bytes
Tue, 14 Apr 2015 10:56:58 -0400 run-tests: fix checking a line to see if it needs globbing
Augie Fackler <augie@google.com> [Tue, 14 Apr 2015 10:56:58 -0400] rev 25059
run-tests: fix checking a line to see if it needs globbing
Tue, 14 Apr 2015 10:14:49 -0400 run-tests: unblock running python tests in python 3
Augie Fackler <augie@google.com> [Tue, 14 Apr 2015 10:14:49 -0400] rev 25058
run-tests: unblock running python tests in python 3 This makes it clear we need to ban os.popen, but we'll do that in a later cleanup.
Mon, 13 Apr 2015 18:07:40 -0400 run-tests: os.popen returns a string, make it bytes again
Augie Fackler <augie@google.com> [Mon, 13 Apr 2015 18:07:40 -0400] rev 25057
run-tests: os.popen returns a string, make it bytes again
Mon, 13 Apr 2015 17:24:10 -0400 run-tests: be more paranoid about os.system using bytes
Augie Fackler <augie@google.com> [Mon, 13 Apr 2015 17:24:10 -0400] rev 25056
run-tests: be more paranoid about os.system using bytes
Mon, 13 Apr 2015 17:17:17 -0400 run-tests: blacklist entries are bytes, use bname to check blacklisting
Augie Fackler <augie@google.com> [Mon, 13 Apr 2015 17:17:17 -0400] rev 25055
run-tests: blacklist entries are bytes, use bname to check blacklisting
Mon, 13 Apr 2015 16:37:53 -0400 test-run-tests.t: work around file.write() returning an int
Augie Fackler <augie@google.com> [Mon, 13 Apr 2015 16:37:53 -0400] rev 25054
test-run-tests.t: work around file.write() returning an int In Python 3.5, file.write() returns the number of bytes it wrote instead of None.
Tue, 14 Apr 2015 16:24:32 -0400 run-tests: write bytes to the binary buffer on sys.{stdout,stderr}
Augie Fackler <augie@google.com> [Tue, 14 Apr 2015 16:24:32 -0400] rev 25053
run-tests: write bytes to the binary buffer on sys.{stdout,stderr}
Tue, 14 Apr 2015 16:21:10 -0400 run-tests: record faildata using bytes instead of str
Augie Fackler <augie@google.com> [Tue, 14 Apr 2015 16:21:10 -0400] rev 25052
run-tests: record faildata using bytes instead of str lines is already bytes, so this is just fixing a bug on python 3.
Tue, 14 Apr 2015 16:18:11 -0400 run-tests: do cdata escaping using bytes instead of str
Augie Fackler <augie@google.com> [Tue, 14 Apr 2015 16:18:11 -0400] rev 25051
run-tests: do cdata escaping using bytes instead of str
Mon, 13 Apr 2015 16:33:12 -0400 run-tests: make sure keyword(s) are in bytes and not str
Augie Fackler <augie@google.com> [Mon, 13 Apr 2015 16:33:12 -0400] rev 25050
run-tests: make sure keyword(s) are in bytes and not str
Mon, 13 Apr 2015 16:31:19 -0400 run-tests: use items instead of iteritems on dicts
Augie Fackler <augie@google.com> [Mon, 13 Apr 2015 16:31:19 -0400] rev 25049
run-tests: use items instead of iteritems on dicts This works the same-enough on 2.6 and 3.5 to be fine.
(0) -10000 -3000 -1000 -300 -100 -60 +60 +100 +300 +1000 +3000 +10000 tip