# # # patch "ChangeLog" # from [ae1b5e9002e3e42e2d21742a0775046264bc3577] # to [e2e59e17744f56b65e2674ff683d3b391b860713] # # patch "monotone.texi" # from [1be851e48f4681094a44ef4d30a5fbefc7985cc3] # to [200d3e76ba97251314502d5e9dd0bdb1215289cb] # ============================================================ --- ChangeLog ae1b5e9002e3e42e2d21742a0775046264bc3577 +++ ChangeLog e2e59e17744f56b65e2674ff683d3b391b860713 @@ -1,3 +1,10 @@ +2006-02-10 Richard Levitte
+ + * monotone.texi (Hooks): Change the example for + get_revisions_cert_trust to check "branch" certs instead of + "ancestor" ones, and thereby match the effect of the "approve" + command. + 2006-02-09 Graydon Hoare * lua.cc (hook_validate_commit_message): make validated the ============================================================ --- monotone.texi 1be851e48f4681094a44ef4d30a5fbefc7985cc3 +++ monotone.texi 200d3e76ba97251314502d5e9dd0bdb1215289cb @@ -6367,8 +6367,8 @@ if t == nil then return false end - if (name ~= "ancestor" and table.getn(t) >= 1) - or (name == "ancestor" and table.getn(t) >= 2) + if (name ~= "branch" and table.getn(t) >= 1) + or (name == "branch" and table.getn(t) >= 2) then return true else @@ -6380,10 +6380,10 @@ In this example, any revision certificate is trusted if it is signed by at least one of three ``trusted'' keys, unless it is an address@hidden certificate, in which case it must be signed by address@hidden certificate, in which case it must be signed by @emph{two} or more trusted keys. This is one way of requiring that -ancestry assertions go through an extra ``reviewer'' before they are -accepted. +the revision has been approved by an extra ``reviewer'' who used the address@hidden command. @item accept_testresult_change (@var{old_results}, @var{new_results})