[prev in list] [next in list] [prev in thread] [next in thread] 

List:       mercurial-devel
Subject:    Re: Evolve 8.4.0 released
From:       Arne Babenhauserheide <arne_bab () web ! de>
Date:       2019-04-15 15:27:15
Message-ID: 87imvf47cc.fsf () web ! de
[Download RAW message or body]

[Attachment #2 (multipart/signed)]


Pierre-Yves David <pierre-yves.david@ens-lyon.org> writes:

> This version brings a variety of improvements and bug fixes. Notably, evolve
> now support smooth automatic resolution of a wider range of divergence
> unstability.
>
> Next evolve version will likely include behavior changes to the ``hg
> evolve``
> command. Making ``--no-update`` and ``--all`` the defaults. For a few
> version,
> users can already rely on ``hg next`` for day to day incremental evolution.

This sounds like evolve is getting ready for being available by default
— is that impression right? Is there a path forward which would make
evolve available to every user of Mercurial?

I'm asking because there is power in defaults. It would mean that every
GUI tool could start adding evolve features without worry that Mercurial
might stop to support it.

And I wouldn't have to search for the right version of evolve for the
installed Mercurial (on different distributions).
Though this is also a reason why merging into Mercurial is only useful
once evolve is conservative enough that we don't need backports of new
features.

Thank you for your great work!

Best wishes,
Arne
--
Unpolitisch sein
heißt politisch sein
ohne es zu merken

["signature.asc" (application/pgp-signature)]
[Attachment #6 (text/plain)]

_______________________________________________
Mercurial-devel mailing list
Mercurial-devel@mercurial-scm.org
https://www.mercurial-scm.org/mailman/listinfo/mercurial-devel


[prev in list] [next in list] [prev in thread] [next in thread]