On Evolve creating too many obsolete commits

Jordi Gutiérrez Hermoso jordigh at octave.org
Fri May 2 12:28:01 CDT 2014


About this section of the wiki (which has turned into an entirely
tl;dr location of weirdly intermeshed rambling, and I'm trying to kill
right now):

    http://mercurial.selenic.com/wiki/EvolveUI#The_obsolete_history_is_not_very_usable

The basic complaint is that since very history-editing operation
creates obsolete commits, this is way too many obsoletes.

At first I thought this was a valid point. Then I realised that we
already have a command for performing complictated multi-step surgery
in one go: histedit. So it seems to me that if you want a complicated
multi-step edition and you don't want to save *every* intermediate
step, you should use histedit.

My suggestion, then, is to have something like hg histedit --start
mode where it saves the initial conditions, lets you do whatever you
want to do DAG, and when you do hg histedit --finish, it only records
the the final state as the replacements of the original state.

Can I kill this rambling section of the wiki with this suggestion?

- Jordi G. H.





More information about the Mercurial-devel mailing list