|
Size: 416
Comment:
|
← Revision 24 as of 2017-08-30 12:42:33 ⇥
Size: 2400
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 1: | Line 1: |
| Most of the name of the writer is Lakesha and she totally loves this name. The thing she adores most is acting but she's been taking on new things these days. Bookkeeping is her profession and she's doing pretty good financially. For a while she's been in Wisconsin. She is working out and maintaining a blog here: http://lopezonzz.tumblr.com/post/58999329627/how-i-built-a-cpanel-hosting-environment-on-aws-part-3 | #pragma section-numbers 2 = Evolve Extension = '''This extension is not distributed along with Mercurial releases''' ''Author: Pierre-Yves David for Various companies'' <<TableOfContents>> (i) This extension enable and enhance the inprogress ChangesetEvolution work. See the dedicated page for details before using it. Code repository: https://www.mercurial-scm.org/repo/evolve/ == Introduction == The `evolve` extension is an experimental implementation of the ChangesetEvolution concept. Most of its content has been moved into core except: * additional history rewriting commands * the evolve command to automatically solve troubles * some user interface warning messages related to obsolete changeset troubles /!\ The evolve extension enables the ChangesetEvolution feature, changing some of Mercurial's default behavior. * history rewriting commands do not strip changesets anymore; they make them obsolete. * history rewriting commands will work on any changesets, possibly creating unstable changesets. * '''pull''' and '''push''' exchange obsolescence data with other evolve-enabled repositories - this may have a performance impact! Current official Documentation: https://www.mercurial-scm.org/doc/evolution/ == Additional Commands == uncommit:: extracts changes from a commit into the working directory, fold:: gathers changes from multiple changesets into a single one, split:: dispatch changes from a single changesets into multiple one, prune:: discards changesets (using obsolescence markers), touch:: replaces a changeset with a different one containing the same payload, but with a different hash, prev:: moves to the parent of the current changeset, next:: moves to the child of the current changeset, evolve:: automatically resolves troubles affecting changesets == Additional UI Messages == * a warning is issued when the current working directory parent becomes obsolete * a warning is issued when a command results in more troubled changesets == Setup == The extension is [[https://pypi.python.org/pypi/hg-evolve|available on PyPi]] To install use {{{ $ pip install --user hg-evolve }}} Then configure your ''`.hgrc`'' to enable the extension by adding the following lines (remember to replace {{{<dir>}}} with the path where you just cloned the extension): {{{ [extensions] evolve = }}} |
Evolve Extension
This extension is not distributed along with Mercurial releases
Author: Pierre-Yves David for Various companies
(i) This extension enable and enhance the inprogress ChangesetEvolution work. See the dedicated page for details before using it.
Code repository: https://www.mercurial-scm.org/repo/evolve/
1. Introduction
The evolve extension is an experimental implementation of the ChangesetEvolution concept. Most of its content has been moved into core except:
- additional history rewriting commands
- the evolve command to automatically solve troubles
- some user interface warning messages related to obsolete changeset troubles
![/!\](/moin-static/modernized/img/alert.png "/!\"){kind=small}
The evolve extension enables the ChangesetEvolution feature, changing some of Mercurial's default behavior.
- history rewriting commands do not strip changesets anymore; they make them obsolete.
- history rewriting commands will work on any changesets, possibly creating unstable changesets.
pull and push exchange obsolescence data with other evolve-enabled repositories - this may have a performance impact!
Current official Documentation: https://www.mercurial-scm.org/doc/evolution/
2. Additional Commands
- uncommit
- extracts changes from a commit into the working directory,
- fold
- gathers changes from multiple changesets into a single one,
- split
- dispatch changes from a single changesets into multiple one,
- prune
- discards changesets (using obsolescence markers),
- touch
- replaces a changeset with a different one containing the same payload, but with a different hash,
- prev
- moves to the parent of the current changeset,
- next
- moves to the child of the current changeset,
- evolve
- automatically resolves troubles affecting changesets
3. Additional UI Messages
- a warning is issued when the current working directory parent becomes obsolete
- a warning is issued when a command results in more troubled changesets
4. Setup
The extension is available on PyPi
To install use
$ pip install --user hg-evolve
Then configure your .hgrc to enable the extension by adding the following lines (remember to replace <dir> with the path where you just cloned the extension):
[extensions] evolve =