Re: [Monotone-devel] code review in practice

[Markus Schiltknecht]

Hi,

Evan Martin wrote:
> Three possibilities I can see:

I'm not sure what you mean by anonymous branches, but there's probably a 
fourth possibility:

Let everyone commit to your main development branch and handle trust by 
using certificates. I.e. if a untrusted developer, commonly known as 
Crazy Bob, commits a revision to 'your' branch, who says you have to use 
and trust that revision? He signed the 'branch' cert,  so its him 
claiming that his revision belongs to that branch. You don't have to 
trust him, or whatever else he has signed.

See the manual for "6.1.5 Trust Evaluation Hooks" [1].

I admit that it's unpleasant to manually "install" these hooks on all 
'clients', so watch out for our Policy Branches!

Regards

Markus

[1]: Monotone Manual - Trust Evaluation Hooks
http://www.monotone.ca/docs/Hooks.html#Hooks