Re: [Monotone-devel] Re: mtn:// sync

[Thomas Moschny]

On Tuesday 25 March 2008, Markus Schiltknecht wrote:
> Thomas Moschny wrote:
> > Any time this comes up, I wonder again, what was the argument for
> > including revs that are ancestors of revs you want to sync, but at then
> > excluding their branch certs? I always found this counterintuitive.
>
> I think that's just an effect of how netsync works, with its separate
> merkle tries for certs and revisions.

Ok. I vaguely had in mind that there also was a non-technical reason.

> > So to me, making "net.venge.monotone" mean "net.venge.monotone.*", does
> > look like an ugly hack to match user's expectations here without
> > addressing the real issue.
>
> Making "net.venge.monotone" mean "that branch and all of its children"
> would result in fetching the associated certs as well, because all child
> branches were included. Thus I even think that would fix the silly issue
> you pointed out above, no?

Exactly, but that's why I said it looks like an ugly hack. It fixes the 
problem accidentally, ...

> (For the common case of syncing "net.venge.monotone", that is).

... and for a common usage pattern, but not fundamentally.

Regards,
Thomas

-- 
Thomas Moschny  <address@hidden>

signature.asc
Description: This is a digitally signed message part.