Obsolete Development
Sean Farley
sean.michael.farley at gmail.com
Tue Aug 7 17:25:03 UTC 2012
> Thanks for your interrest in evolve!
Thanks to you and Patrick (and unnamed others, I'm sure) for answering
and providing the patches.
> Both document and code are hosted on bitbucket:
>
> https://bitbucket.org/marmoute/hgview-mutable
>
> Contribution can be submitted by pull request from either bitcket or obsolete
> enabled repo[1].
Ok, will do. I have a lot of feedback for documentation, mostly, and
some for code but I'm still new to the codebase and it's a little much
for me right now. I will try to at least provide some tracebacks.
> I believe that discussion can happen on the mercurial list for now. We'll move
> to a dedicated list if the amount get out of control. As a lot of code are
> aimed for code, UI and terminolgy discussion deserves to happen on this list
> anyway.
First of all, using evolve is amazingly powerful and is a breath of
fresh air coming from using mq. As has been mentioned by others
before, I don't quite know what to do about the abandoned changesets.
So far, they get in the way of
1) histedit (aborts because of orphaned nodes)
2) local numbering is out-of-whack (these have been left out of the
documentation I guess for this reason?)
If I haven't pushed to anywhere, I usually run:
$ hg strip -r 'hidden()'
and that seems to work. So far, this has worked in my simple test
cases even with pushing to other repos but is there a danger to
stripping these changesets?
More information about the Mercurial-devel
mailing list