[PATCH 6 of 8] obsolete: exchange obsolete marker over pushkey

[Pierre-Yves David]

Quick reply as I see Idank dig into "imaginary" design issue

On Fri, Jun 08, 2012 at 02:25:59PM +0200, Patrick Mézard wrote:
> Le 08/06/12 13:25, Idan Kamara a écrit :
> > On Fri, Jun 8, 2012 at 1:28 PM, Patrick Mézard <patrick at mezard.eu> wrote:
> >>
> >> Le 08/06/12 11:50, Idan Kamara a écrit :
> >>> On Thu, Jun 7, 2012 at 8:56 PM, Patrick Mézard <patrick at mezard.eu>
> >>> wrote:
> 
> [...]
> 
> >>> 1) does the 'obsstore' ever shrink or does it grow indefinitely?
> >>
> >> It grows indefinitely. This may not be as bad as it sounds in practice,
> >> there are two extreme cases:
> >> - Public repositories. They should accept only "killing" markers.
> 
> (Note the statements above belong to me, I am sure Pierre-Yves has a different take on this).

All repo keep all marker: (not just kill one)

In the phares above you means "Publishing repository (with public phase only content)" not "Public"


Most repo can decide to garbage collected marker that both:

- are relevant to changeset where the newest version are public

- are older that N month

This garbage collection can be done with no side effect in 95% of the case. If
someone kept old draft version somewhere which are infact obsolete it will have
it as a duplicate (as both mercurial and git handle it now)

-- 
Pierre-Yves David

http://www.logilab.fr/

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: Digital signature
URL: <http://selenic.com/pipermail/mercurial-devel/attachments/20120608/51c52f16/attachment.pgp>