[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Monotone-devel] Approval revisited...
From: |
Timothy Brownawell |
Subject: |
Re: [Monotone-devel] Approval revisited... |
Date: |
Fri, 10 Feb 2006 15:15:13 -0600 |
On Fri, 2006-02-10 at 19:26 +0100, Richard Levitte - VMS Whacker wrote:
> I've been rethinking. Ignore that, changing the approve command will
> not really make things better, because then we need to check that the
> value of an "approved" cert matches any available "branch" cert or the
> current branch, and that would require something quite a bit more
> complex than the current get_revision_cert_trust hook.
>
> What would be needed is perhaps have approve avoid adding a branch
> cert for a branch the revision isn't already in...
Um, I think that's the entire purpose of approve. It basically says, "I,
so-and-so, approve revision xxxxxxxx for inclusion into branch
aaaa.bbbb.cccc.".
Tim
- [Monotone-devel] Approval revisited..., Richard Levitte - VMS Whacker, 2006/02/10
- Re: [Monotone-devel] Approval revisited..., Richard Levitte - VMS Whacker, 2006/02/10
- Re: [Monotone-devel] Approval revisited...,
Timothy Brownawell <=
- Re: [Monotone-devel] Approval revisited..., Richard Levitte - VMS Whacker, 2006/02/10
- Re: [Monotone-devel] Approval revisited..., Timothy Brownawell, 2006/02/10
- Re: [Monotone-devel] Approval revisited..., Daniel Carosone, 2006/02/10
- Re: [Monotone-devel] Approval revisited..., Richard Levitte - VMS Whacker, 2006/02/10
- Re: [Monotone-devel] Approval revisited..., Bruce Stephens, 2006/02/10
Re: [Monotone-devel] Approval revisited..., Nathaniel Smith, 2006/02/11