Copy that. Thanks Sitaram. 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. Regards, Johnny On Tue, Jan 6, 2009 at 7:57 PM, Sitaram Chamarty <sitaramc@xxxxxxxxx> wrote: > On 2009-01-06, Jeff King <peff@xxxxxxxx> wrote: >> If you are going to have multiple users sharing a repository, generally >> they should be in the same group and the core.sharedrepository config >> option should be set (see "git help config", or the "shared" option to >> git-init). >> >> I've never used that personally, though. I have always just used POSIX >> ACLs, with a default ACL on each directory giving access to everyone. >> E.g. (off the top of my head): >> >> for user in user1 user2 user3; do >> setfacl -R -m u:$user:rwX -m d:u:$user:rwX /path/to/repo >> done > > 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. > > Works fine for small teams... > > -- > 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 > -- we all have our crosses to bear -- 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
