Sun, 01 Oct 2017 11:58:27 +0100 extdata: just use iterator to read lines one by one
Yuya Nishihara <yuya@tcha.org> [Sun, 01 Oct 2017 11:58:27 +0100] rev 34461
extdata: just use iterator to read lines one by one
Sun, 01 Oct 2017 11:56:41 +0100 extdata: ignore ambiguous identifier as well
Yuya Nishihara <yuya@tcha.org> [Sun, 01 Oct 2017 11:56:41 +0100] rev 34460
extdata: ignore ambiguous identifier as well
Sun, 01 Oct 2017 11:13:09 +0100 templater: add experimental support for extdata
Yuya Nishihara <yuya@tcha.org> [Sun, 01 Oct 2017 11:13:09 +0100] rev 34459
templater: add experimental support for extdata This is minimal and non-controversial implementation of extdata() template function. Originally extdata sources were exposed to the keyword namespace, but I've changed it to a plain function for simplicity.
Sun, 01 Oct 2017 10:50:00 +0100 revset: add experimental support for extdata
Yuya Nishihara <yuya@tcha.org> [Sun, 01 Oct 2017 10:50:00 +0100] rev 34458
revset: add experimental support for extdata This is minimal and non-controversial implementation of extdata() revset. Originally extdata sources were exposed to the symbol namespace, but I've changed it to a plain function for simplicity.
Tue, 13 Sep 2016 14:14:05 -0500 extdata: add extdatasource reader
Matt Mackall <mpm@selenic.com> [Tue, 13 Sep 2016 14:14:05 -0500] rev 34457
extdata: add extdatasource reader This adds basic support for extdata, a way to add external data sources for revsets and templates. An extdata data source is simply a list of lines of the form: <revision identifier>[<space><freeform text>]\n An extdata source is configured thusly: [extdata] name = <a url or path> urls of the form shell: are launch shell commands to generate data. This patch is slightly modified by Yuya Nishihara as follows: - fix typo - remove unused function - remove future expansion point for parameter (which can be added later as the extdata revset/template are experimental) You can see the original patch at https://www.mercurial-scm.org/pipermail/mercurial-devel/2016-September/088426.html
Wed, 04 Oct 2017 10:02:15 +0200 tests: change to parent directory before all "hg init" in test-log.t
Denis Laxalde <denis.laxalde@logilab.fr> [Wed, 04 Oct 2017 10:02:15 +0200] rev 34456
tests: change to parent directory before all "hg init" in test-log.t Add a "cd .." before the second "hg init" so that all repositories are on top level of test directory. Makes inspection of test directory easier.
Tue, 03 Oct 2017 12:00:07 -0700 config: add a missing preparewrite() call
Jun Wu <quark@fb.com> [Tue, 03 Oct 2017 12:00:07 -0700] rev 34455
config: add a missing preparewrite() call Thanks Yuya for pointing this out in D808. Differential Revision: https://phab.mercurial-scm.org/D924
Tue, 03 Oct 2017 16:59:17 -0700 test-strip: make test compatible with chg
Saurabh Singh <singhsrb@fb.com> [Tue, 03 Oct 2017 16:59:17 -0700] rev 34454
test-strip: make test compatible with chg The test was using reposetup which had the logic for stripping commits. This leads to a situation where if the reposetup was called twice for an extension (which can happen with chg running), the stripped node would not be found the second time. Therefore, this commit changes the test to put the stripping logic inside commands instead of the reposetup. This ensures that the stripping logic is invoked only when the command is invoked and thus, avoids any problems. Test Plan: Ran the test 'test-strip.t' with and without the '--chg' option. Differential Revision: https://phab.mercurial-scm.org/D928
Tue, 03 Oct 2017 14:35:24 -0700 test-hook: make test compatible with chg
Saurabh Singh <singhsrb@fb.com> [Tue, 03 Oct 2017 14:35:24 -0700] rev 34453
test-hook: make test compatible with chg The test uses the 'print' method instead of writing to stdout using 'ui.write' which leads to incompatibility with chg. This commit modifies the test to use 'ui' instead which fixes the problem. Test Plan: Ran the test 'test-hook.t' with and without '--chg' option. Differential Revision: https://phab.mercurial-scm.org/D927
Tue, 03 Oct 2017 13:30:36 -0700 test-setdiscovery: make test compatible with chg
Saurabh Singh <singhsrb@fb.com> [Tue, 03 Oct 2017 13:30:36 -0700] rev 34452
test-setdiscovery: make test compatible with chg The test checks the output of the blackbox extension which will contain logs corresponding to chg in case chg is running. Therefore, this commit modifies the test to take chg into consideration while working with the blackbox extension. Test Plan: Ran the test 'test-setdiscovery.t' with and without the '--chg' option. Differential Revision: https://phab.mercurial-scm.org/D926
(0) -30000 -10000 -3000 -1000 -300 -100 -10 +10 +100 +300 +1000 +3000 +10000 tip