You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@subversion.apache.org by James Courtier-Dutton <Ja...@superbug.co.uk> on 2007/03/07 17:00:25 UTC
Authorising commits
Hi,
Is there any way to require 3 different people to authorise a change
before it gets commited.
This would need the first person to submit a change, but the change
would require 2 other people signing it before it gets committed to the
repository.
James
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: Authorising commits
Posted by Daniel Rall <dl...@collab.net>.
On Wed, 07 Mar 2007, James Courtier-Dutton wrote:
> Hi,
>
> Is there any way to require 3 different people to authorise a change
> before it gets commited.
> This would need the first person to submit a change, but the change
> would require 2 other people signing it before it gets committed to the
> repository.
Hi James. The topic of this mailing list is the development of
Subversion itself. This type of message is more appropriate for the
users mailing list.
There isn't currently a way to programmatically do what you suggest.
You could model this workflow using a branch-based changeset promotion
model, where incoming changes go into a holding branch waiting
approval, after which they're merged into the mainline. To support
this type of model, you'd probably want to use a tool like
svnmerge.py, or possibly svk, until Subversion has its own Merge
Tracking support.