Obsolete Development

[Sean Farley]

> Beware that I'm currently doing a major cleanup for the obsolete and evolve
> code base (I may even merge them both). You may want to hold yourself a few day
> before working in the code.
>
> This does not apply to document ion.

Gotcha. I'll hold off for now. It would be great if this was all one extension!

> I plan to work on histedit obsolescence aware soon™

Fair enough.

> Yeah, I do not think this will change. People should not rely on local
> numbering too much. Moreover this local numbering make sense when you use
>
>     hg log --hidden

That much I saw, yeah. The local numbering, though, is really
convenient for specifying a revision for any number < 100,000,000,000
(based off a unique 12-character hashed prefix). Maybe something like
bash completion would help but I don't know. Perhaps it is possible to
drop local revision numbering with better revset notation in my custom
log template. Any tips for this would be greatly appreciated :-)

Also, it's a little odd that if you specify 'hidden()' you still have
to provide --hidden:

$ hg log --hidden -r 'hidden()'

I don't know if there's an easy fix or not for this.

> There is not danger exect the fact you "loose" your backup and ability to
> consulte rewritting history.

I see.

> Note: I'm interrested in people keeping their extinct changeset for performance
>       impact.

Ok, I'll keep them around and let you know.