[Top][All Lists]

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

[Monotone-devel] Re: version 1.14 fails "make check"

From: Peter Simons
Subject: [Monotone-devel] Re: version 1.14 fails "make check"
Date: 15 Aug 2004 15:20:06 +0200

Richard Levitte writes:

 >> In _my_ case, the current branch is important. I want to
 >> say: In branch "foo" we'll trust key "bar".

 > The thing is, as I understand it, is that the "current"
 > branch is only an attribute of your working directory,
 > and has absolutely nothing to do with the contents of the
 > database.

Yes, you are right. But that doesn't really affect my use
case. I want to say: In branch "foo" we'll trust key "bar".
Period. And that's not possible with the current model,
unless I have a monotonerc file per branch. But I want a
global one. 

 > Do you want a specific branch that you and all those you
 > trust know the name of [...] or do you want to have extra
 > control on the current branch in your work directory
 > [...]?

I would like to have one global monotonerc file -- say
$HOME/.monotonerc --, and in it I want to determine which
keys are trusted in which branch; completely independent of
the database I use.

 >   function get_manifest_cert_trust (signers, id, name, val)
 >     local foo_trusted_signers = { "address@hidden", ... }

 >     local t_foo = intersection(signers, foo_trusted_signers)
 >     if t_foo ~= nil
 >     then
 >       if name == "branch" and val == "foo" and table.getn(t_foo) >= 1
 >       then
 >         return true
 >       end
 >     end

 >     return false
 >   end

I am not certain what this code does, actually. Won't this
leave any other certificate (say, ancestor) untrusted?


reply via email to

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