Differences between revisions 1 and 5 (spanning 4 versions)
Revision 1 as of 2013-02-01 22:36:18
Size: 1392
Comment: initial stub
Revision 5 as of 2013-02-09 11:00:27
Size: 1404
Comment: fix list
Deletions are marked like this. Additions are marked like this.
Line 2: Line 2:
= Rebase Extension = = Evolve Extension =
Line 16: Line 16:
* 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,
Line 24: Line 24:
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 31:
evolve:: automatically solve troubles affecting changesets  evolve:: automatically solve troubles affecting changesets
Line 35: Line 35:
* 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

Evolve Extension

This extension is not distributed along with Mercurial releases

Author: Pierre-Yves David for Logilab

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

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,

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

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