RoadMap for Obsolete Marker

[Patrick Mézard]

Le 11/05/12 22:40, Pierre-Yves David a écrit :
> This afternoon Matt, David, Augie and I talked about Obsolete Markers. MWe
> mostly talk about their Definition, Storage and Exchange.

[...]

> II) Exchange
> -------------------------
> 
>     Finding and efficient way to exchange Obsolete marker between repository is
>     complete.
> 
>     * Obsolete markers are not related to each other as changeset are.
> 
>     * You can't never safely delete Obsolete Marker so the amount of them grow with
>       the repository.
> 
>     A solution adding "generation number" to obsolete marker may have been
>     found. I'll write another email with detail later.

1- If I "hg push --rev", do I have to sent more revisions than rev and its ancestors?

I suppose not, if stabilize strategy rely on merging replacement revs with descendants of obsoleted ones. Do you have a summary of stabilize heuristic?

2- If only public and draft revisions can be exchanged, I suppose only obsolete information about public and draft revision has to be exchanged?

If I am not wrong, changesets are created as "draft" by default. So, if I create a local changeset and amend it several times, I will send obsolete information related to all the (obsolete, never to be seen) amended changesets as well?

--
Patrick Mézard