"Robin H. Johnson" [off-list ref] wrote:
On Wed, Jun 03, 2009 at 10:27:02PM +0200, Heiko Voigt wrote:
quoted
You are welcome. An interesting addition would be to propagate allowed
branchnames from gitosis.conf. That way you can implement write-
protected branches using an update hook.
...
quoted
A nice solution to steer this directly from gitosis.conf? I never got
around implementing it.
Has anybody implemented something like cvs_acls.pl (used by FreeBSD) for
Git?
contrib/hooks/update-paranoid ?
Perhaps the most flexible, and most paranoid, update hook available.
But it does require that the frontend set some sort of user identity.
I think it relies on UNIX uid, but its easy to hack to use an env
var instead from gitosis.
--
Shawn.