About evolve extension

[Andrew Fischer]

For what it's worth my experience with the evolve extension has been
similar, though my use cases are simpler. Is there some sense of how far
away it is from being included with mercurial? I can't wait till it sees
wider adoption.

On Wed, Dec 21, 2016 at 2:51 AM, Arne Babenhauserheide <arne_bab at web.de>
wrote:

> Hi Jan,
>
> Thank you for your report!
>
> I’m forwarding your mail to the evolve-testers list (see the
> recipients).
>
> Best wishes,
> Arne
>
> Jan Vrany writes:
>
> Hi,
>
> I'd like to share my experience.
>
> I'm using evolve extension extensively for more than
> a year now in a not-so-trivial setup (multiple
> shared repositories on development machine then pushed
> to staging server 1 then pushed to staging server 2,
> bug found there, amend on my machine, push amended
> changeset to staging 1, then staging 2...that sort of
> things).
>
> Ever since I started using it I don't remember a single
> moment like "Ug, what's going on here?" It always did what
> I expected. I never bothered to study the internals or
> the documentation because it just works for me and always
> behaved well. It might have rough edges here and there - but
> I never saw them.
>
> Evolve is really a killing feature for me. Is well
> engineered with clean and simple user interface.
>
> Many, many thanks to all who worked hard to make
> my life easy and fun :-) Well done, guys!
>
> Best, Jan
>
> --
> Unpolitisch sein
> heißt politisch sein
> ohne es zu merken
>
> _______________________________________________
> Mercurial mailing list
> Mercurial at mercurial-scm.org
> https://www.mercurial-scm.org/mailman/listinfo/mercurial
>
>


-- 
Andrew Fischer
Apastron Co
903 1st ST N Hopkins, MN
952-373-1024
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mercurial-scm.org/pipermail/mercurial/attachments/20161221/f3ecb25b/attachment-0002.html>