How to unhide a hidden (obsolete) changeset?

[Pierre-Yves David]

On 02/01/2014 05:13 PM, Michael McNeil Forbes wrote:
>
> On Feb 1, 2014, at 5:01 PM, Pierre-Yves David <pierre-yves.david at ens-lyon.org> wrote:
>
>> If you want B to looks like A you could:
>>
>> 1) strip any hidden changeset in B `hg strip --hidden 'hidden()'`
>> 2) remove all obsolesnce marker in B `mv .hg/store/obstore .hg/store/obstore.foo`
>> 3) repull from A `hg pull A`
>
> That is what I was looking for.
>
> Could you point me to the documentation about the format of this file?
> (I have a strong and I am sure unadvisable desire to delete portions
> of this file to unhide a couple change sets manually.  Is that even
> possible?  Playing a bit it sort of seems so, but I expect to shoot
> myself in the foot any moment now:-)

Theformat is mostly binary giberish, I do not advice you to try playing 
with it.

http://www.selenic.com/hg/file/9139dedeffa6/mercurial/obsolete.py#l55

If you insist, I would however accept patch for a sensible 
`debugstripobsolescencemarker` function

Thanks for you interrest in evolve

-- 
Pierre-Yves