On Wed, Mar 22, 2017 at 4:59 PM, Sean Farley <s...@farley.io> wrote: >>> > By the way, I'm not sure if you have noticed that "inhibit" was recently >>> > moved to a directory called "hack/" in mutable-history. >>> >>> Yes, things in evolve are still baking. I don't see the need to rush obs >>> cycles into core based on that, though. >> >> Shall we have "unamend", "unrebase", "unhistedit" and "undo" ready, please >> do not use them as you don't need them. > > But that's part of the problem: all the edge cases mentioned here will > affect normal use of obs markers. Why not put this in an extension for > now? I don't see how this is more important than fixing terminology / > error messages / UI / UX / etc etc etc.
I'm deeply sympathetic to the desire to "just roll back to an old version of this" and not have the hash change, and I'm also extremely sympathetic to the idea that cycles should have an obvious, easy way to recover. Something like what Jun has proposed in this series strikes me as the least-awful option to date, though I haven't considered it as much as I'm sure Jun and Pierre-Yves have. _______________________________________________ Mercurial-devel mailing list Mercurial-devel@mercurial-scm.org https://www.mercurial-scm.org/mailman/listinfo/mercurial-devel
