Am 03.11.2011 08:17, schrieb Magnus Bäck: > On Thursday, November 03, 2011 at 07:10 CET, > redhat1981 <redhat1981@xxxxxxxxx> wrote: >> Inside the repository, testabc let us say there are folders folder1, >> folder 2 etc, I want some users to have read/write, read or no access >> to the folder1 or folder2, Is this possible in Git, I have done it in >> SVN, Please help!! > > Given Git's nature, you can't have read access restrictions on a sub-git > level (i.e. file/directory level). For basically the same reason, you > can never prevent users from making (local) commits that modify certain > paths (but you can encourage people to have local hooks to enforce such > policies). What you *can* do is install a server-side update hook that > rejects attempts to push commits that modify certain paths. If you're > willing to trade Gitosis for Gitolite, you get that feature for free. Directory read access control can be achieved by putting the directory content into a submodule. You can then control who is allowed to clone from the repo for that submodule separately from the superproject, thereby disallowing a group of people to see (let alone modify) what is in there. http://progit.org/book/ch6-6.html -- 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