Re: [Monotone-devel] mtsh, monotree, monotone.el, etc.

[Nathaniel Smith]

On Wed, Feb 08, 2006 at 06:09:13PM +0000, Bruce Stephens wrote:
> But wouldn't it be neat if somehow one could control trust based on
> path?  For example you might give a whole bunch of people the ability
> to change things in contrib, but not necessarily want all of them to
> change things in the rest of monotone.  
> 
> I imagine that could work by letting get_revision_cert_trust know
> which files a revision changes, but beyond that I'm less sure.

You can't do that, really; get_revision_cert_trust gets called too
often to be calculating complicated information to pass it :-).

(E.g., "heads", and operations that call "heads" as a subroutine like
checkout, call get_revision_cert_trust on _every single branch cert on
the given branch_.)

This reminds me of another reason why declarative trust rules in a
specially constructed branch is a nice design: it can go _much_
faster, because we can do intelligent caching of trust.

(E.g., "heads" can become O(1) and instantaneous.  And more
complicated trust rules become acceptably performant, because you
only have to check them once.)

-- Nathaniel

-- 
So let us espouse a less contested notion of truth and falsehood, even
if it is philosophically debatable (if we listen to philosophers, we
must debate everything, and there would be no end to the discussion).
  -- Serendipities, Umberto Eco