Differences between revisions 1 and 7 (spanning 6 versions)
⇤ ← Revision 1 as of 2013-02-01 22:36:18 →
Size: 1392
Editor: Pierre-YvesDavid
Comment: initial stub
← Revision 7 as of 2013-02-09 12:54:38 → ⇥
Size: 2173
Editor: tonfa
Comment:
Deletions are marked like this. Additions are marked like this.
Line 2: Line 2:
= Rebase Extension = = Evolve Extension =
Line 12: Line 12:
Code repository: https://bitbucket.org/marmoute/mutable-history
Line 16: Line 18:
* additional history rewriting commands
* the evolve command to automatically solves troubles
* some user interface warning messages related to obsolescence changesets troubles,		  * additional history rewriting commands
 * the evolve command to automatically solves troubles
 * some user interface warning messages related to obsolescence changesets troubles,

/!\ The evolve extension enables ChangesetEvolution feature. Changing somes of default Mercurial behavior.

* history rewriting commands do not strip changesets anymore, they turn them obsolete.
* history rewriting commands accept to work on any changesets possibly creating unstable changesets
* pull and push exchanges obsolescence data with other evolve enabled repository (This may have performance impact)
Line 24: Line 32:
uncommit:: extracts changes from a commit
fold:: gather changes from multiple changesets in a single one
prune:: discard changesets (using obsolescence marker)
touch:: replace a changesets with one with the same payload but with a different node
gdown:: move to the parent of the current checkout changeset
gdown:: move to the children of the current checkout changeset		  uncommit:: extracts changes from a commit
 fold:: gather changes from multiple changesets in a single one
 prune:: discard changesets (using obsolescence marker)
 touch:: replace a changesets with one with the same payload but with a different node
 gdown:: move to the parent of the current checkout changeset
 gdown:: move to the children of the current checkout changeset
Line 31: Line 39:
evolve:: automatically solve troubles affecting changesets  evolve:: automatically solve troubles affecting changesets
Line 35: Line 43:
* issue a warning when current working directory parent becomes obsolete
* issue a warning when a commands result in more troubled changesets		  * issue a warning when current working directory parent becomes obsolete
 * issue a warning when a commands result in more troubled changesets

== Setup ==


Setting up the evolve extension is simple:

{{{
  $ hg clone https://bitbucket.org/marmoute/mutable-history -u stable
  $ echo '[extensions]\nevolve=$PWD/mutable-history/hgext/evolve.py' >> ~/.hgrc
}}}

/!\ Evolve requires the latest Mercurial version: 2.5

Evolve Extension

This extension is not distributed along with Mercurial releases

Author: Pierre-Yves David for Logilab

Contents

  1. Introduction
  2. Additional Commands
  3. Additional UI Messages
  4. Setup

/!\ This feature is experimental to be used only by experienced Mercurial user that understand underlying concept

Code repository: https://bitbucket.org/marmoute/mutable-history

1. Introduction

The evolve extension is an experimental implementation of the ChangesetEvolution concept. Most of it's content have been moved into core except:

  • additional history rewriting commands
  • the evolve command to automatically solves troubles
  • some user interface warning messages related to obsolescence changesets troubles,

/!\ The evolve extension enables ChangesetEvolution feature. Changing somes of default Mercurial behavior.

* history rewriting commands do not strip changesets anymore, they turn them obsolete. * history rewriting commands accept to work on any changesets possibly creating unstable changesets * pull and push exchanges obsolescence data with other evolve enabled repository (This may have performance impact)

Current official home page: http://hg-lab.logilab.org/doc/mutable-history/html/

2. Additional Commands

uncommit
extracts changes from a commit
fold
gather changes from multiple changesets in a single one
prune
discard changesets (using obsolescence marker)
touch
replace a changesets with one with the same payload but with a different node
gdown
move to the parent of the current checkout changeset
gdown
move to the children of the current checkout changeset
evolve
automatically solve troubles affecting changesets

3. Additional UI Messages

  • issue a warning when current working directory parent becomes obsolete
  • issue a warning when a commands result in more troubled changesets

4. Setup

Setting up the evolve extension is simple: 

  $ hg clone https://bitbucket.org/marmoute/mutable-history -u stable
  $ echo '[extensions]\nevolve=$PWD/mutable-history/hgext/evolve.py' >> ~/.hgrc

/!\ Evolve requires the latest Mercurial version: 2.5

EvolveExtension (last edited 2017-08-30 12:42:33 by RyanMcElroy)