Using changeset obsoletion with Kallithea
Thomas De Schampheleire
patrickdepinguin at gmail.com
Mon May 30 15:21:16 UTC 2016
>>>
>>> Oh, and the last thing: how to get that cool thing. Just put this into
>>> your hgrc:
>>>
>>> [experimental]
>>> evolution = all
>>>
>>
>> What exactly does this bring on top of vanilla Mercurial? And where is
>> this setting defined?
>> Are you sure it is still relevant with recent versions of Mercurial, say 3.7+ ?
>
> This is definitely still needed in Mercurial 3.7, I have just checked
> mercurial/obsolete.py. This setting enables the creation and exchange of
> obsolete markers. As I understand it, unless exchange is enabled, you
> won't push any markers, and unless creation is enabled, commit --amend,
> histedit and rebase use strip to edit history. The markers will still be
> interpreted, as I understand it.
>
>> I don't have this setting and use rebase/histedit, and do see obselete
>> changes with 'log --hidden'.
I see what happened: I did enable evolve in my repo's hgrc.
>
>>> Optionally, also this, where applicable:
>>>
>>> [phases]
>>> publish = False
>>
>> Thanks for writing all this.
>> What is the plan with this text, will we publish it somewhere?
>
> I think if my code gets merged, we may add some version of the text
> above to the documentation.
I'll give some feedback on the text itself later...
/Thomas
More information about the kallithea-general
mailing list