Mercurial > evolve
view hgext3rd/topic/README @ 4722:7839720c7c75
rewind: make sure merge commits include files from p1 and p2
Otherwise rewinding a merge commit makes it lose all changes.
This fix populates `updates` argument of rewriteutil.rewrite() with parent
changesets. That argument is normally used for folding multiple changesets, but
in this case it's simply used to include files from p1 and p2. Usually,
rewrite() works fine using ctx.files(), but that function can return an empty
list when ctx is a merge commit.
author | Anton Shestakov <av6@dwimlabs.net> |
---|---|
date | Thu, 11 Jul 2019 17:04:08 +0800 |
parents | 13751fef5e66 |
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.