New user guide for evolve
Angel Ezquerra
angel.ezquerra at gmail.com
Sun Apr 27 19:48:31 UTC 2014
On Sun, Apr 27, 2014 at 9:45 PM, Greg Ward <greg at gerg.ca> wrote:
> On 27 April 2014, Angel Ezquerra said:
>> > Some of the things you can do with ``evolve`` are:
>> >
>> > * fix a mistake immediately: "oops! I just committed a changeset
>> > with a syntax error -- I'll fix that and amend the changeset so no
>> > one sees my mistake"
>>
>> I don't think this example highlights any new feature introduced by
>> evolve. Can't you already do this without evolve?
>> Maybe you should say that this keeps the old version around, or that
>> you can fix a _pushed_ revision as long as the remote repo is non
>> publishing.
>
> It's true that this has been possible forever with "hg rollback", and
> for a while with "hg commit --amend". I was trying to keep it short
> and simple and not confuse matters with precise legalistic wording.
> But I think this might work:
>
> * Fix a mistake immediately: "oops! I just committed a changeset
> with a syntax error -- I'll fix that and amend the changeset so no
> one sees my mistake". (While this is possible using existing
> features of core Mercurial, ``evolve`` makes it safer.)
>
> Anyone have a better suggestion?
>
> Thanks for the feedback!
I think that's better. Perhaps you could say:
"While this is possible using existing features of core Mercurial,
``evolve`` makes it safer by keeping the original changeset around,
albeit hidden and marked obsolete)"
Cheers,
Angel
More information about the Evolve-testers
mailing list