Mercurial > evolve
view README-topic @ 2926:1abafae41fe2
evolve: use registrar.templatekeyword to register template keyword functions
Now, using registrar.templatekeyword of Mercurial directly in evolve
extension should be safe enough. because it has been available since
Mercurial 3.8, and minimum Mercurial version for evolve extension is
3.8, too.
BTW, this also fixes an issue of "hg help templates" output that
template keywords "precursors" and "successors" are not displayed as
same as others, because they do not have ":KEYWORD:" prefix in their
docstring.
author | FUJIWARA Katsunori <foozy@lares.dti.ne.jp> |
---|---|
date | Mon, 07 Aug 2017 23:22:41 +0900 |
parents | 47017b3086d4 |
children |
line wrap: on
line source
Topic Extension ================ This packages also provides the ``topic`` experiment in an independent extension. It implements a new experimental concept to provide lightweight feature branches for the mutable parts of the history. The experiments is still at an early stage and have significant usability and performance issues when enabled. How to Install ============== The ``topic`` extension is included into the ``evolve` package, so the same instruction apply. Using Pip --------- You can install the latest version using pip:: $ pip install --user hg-evolve Then just enable it in you hgrc:: $ hg config --edit # adds the two line below: [extensions] topic = From Source ----------- To install a local version from source:: $ hg clone https://www.mercurial-scm.org/repo/evolve/ $ cd evolve $ make install-home Enable ------ The topic extensions is included in the evolve package. See the install instruction for evolve. Then enable it in you configuration:: $ hg config --edit # adds the two line below: [extensions] topic = Documentation ------------- * See 'hg help -e topic' for a generic help. * See 'hg help topics' and 'hg help stack' for help on specific commands. * See the 'tests/test-topic-tutorial.t' file for a quick tutorial.