I assume that you're talking about this update-paranoid hook in Git's 
'contrib' sources:


It looks a bit old, and complicated. You may want to check out 
Gitolite<https://github.com/sitaramc/gitolite> which 
is under active development. I've heard it supports access control very 
well, and is quite easy to get started with. Haven't used it myself though.

Tuesday, June 19, 2012 11:57:36 PM UTC+2, jurgen wrote:
> I would like to use the update-paranoid hook to prohibit pushing to the 
> master branch, yet I could not find any information of how to setup the 
> hook.
> The documentation in the hook script talks about user specific ACL files, 
> but I have no idea where to put these files. Also, nothing is said of how 
> to use groups. Does anybody have some clues? How are the ACL files 
> organized (in which repositories, etc.).
> Thanks for your help.

You received this message because you are subscribed to the Google Groups "Git 
for human beings" group.
To view this discussion on the web visit 
To post to this group, send email to git-users@googlegroups.com.
To unsubscribe from this group, send email to 
For more options, visit this group at 

Reply via email to