On 2009-01-06, Johnny Lee <johnnylee194@xxxxxxxxx> wrote: > On Tue, Jan 6, 2009 at 7:57 PM, Sitaram Chamarty <sitaramc@xxxxxxxxx> wrote: >> If you're not worried about the finer-grained access control >> that acl(5) gives you, just do what "git init >> --shared=group" does: >> >> git config core.sharedrepository 1 # as mentioned above >> chmod g+ws .git >> >> Now set the group to something (I use "gitpushers" ;-) >> >> chgrp -R gitpushers .git >> >> amd make sure all your users are part of that group. > We also plan to do it in this way, just a small wondering that it > looks a kind of workaround instead of a more graceful solution. I wouldn't consider it a workaround. It uses normal Unix permissions the way they were designed to, including setgid for directories. Actually, I am yet to come up with a situation where I actually needed ACLs, though they are more generalised, and fine-grained. And the maint is all eminently scriptable. -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
