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

[Koen Kooi]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Thomas Keller schreef:
> 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)?

How does it handle this:

mtn co -r<rev before I got banned> ; <mayhem> ;mtn commit ?

regards,

Koen
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (Darwin)

iD8DBQFE/9XBMkyGM64RGpERAnvQAJ4+helelfdaSnil93cAVBJqtEkgcACfW+y0
IZNlwCxJYIWvNik7AWgb4yg=
=P2vG
-----END PGP SIGNATURE-----