[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Monotone-devel] [RFC] versioned policy -- introduction

From: Nathaniel Smith
Subject: Re: [Monotone-devel] [RFC] versioned policy -- introduction
Date: Thu, 7 Sep 2006 02:40:40 -0700
User-agent: Mutt/1.5.12-2006-07-14

On Thu, Sep 07, 2006 at 09:50:02AM +0200, Thomas Keller wrote:
> Nathaniel Smith schrieb:
> > We call the user-specified revid the "trust seed".  The "seed" part
> > emphasises that we are not (necessarily) trusting the tree we point
> > to in particular.  Rather, one of the things a tree should have ACLs
> > for, is specifying who is allowed to commit _new trust trees_.  The
> > simplest way to do this is to put the trust trees in a special branch,
> > and specify commit access to this branch like any other branch.
> So if I understand this correctly, the commit access to the trust tree
> is defined by the trust tree itself? Is this not some chicken-egg
> problem? Or is monotone then delivered with a "default" tree (or has
> some command which can build such a tree)?

The seed lets you bootstrap -- whatever revision is given in the seed
is trusted, a priori.  Then we can use whatever rules it says to
figure out what the next trusted revision, and so on and so forth.

-- Nathaniel

"Of course, the entire effort is to put oneself
 Outside the ordinary range
 Of what are called statistics."
  -- Stephan Spender

reply via email to

[Prev in Thread] Current Thread [Next in Thread]