From: "Magnus Bäck" <magnus.back@sonyericsson.com>
To: redhat1981 <redhat1981@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: Folder level Acces in git
Date: Thu, 3 Nov 2011 08:17:01 +0100 [thread overview]
Message-ID: <20111103071701.GA22412@jpl.local> (raw)
In-Reply-To: <1320300655224-6958047.post@n2.nabble.com>
On Thursday, November 03, 2011 at 07:10 CET,
redhat1981 <redhat1981@gmail.com> wrote:
> I am using Gitosis, Adding the gitosis conf file
>
> [group testabc]
> writable = testabc
> members = shrii Abhijeet premkumar
> add cgit = yes
> gitweb = yes
>
>
> [group testabc-readonly]
> readonly = testabc
> members = Ganesh Shweta
> add cgit = yes
> gitweb = yes
>
> 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.
http://book.git-scm.com/5_git_hooks.html
http://progit.org/book/ch4-8.html
--
Magnus Bäck Opinions are my own and do not necessarily
SW Configuration Manager represent the ones of my employer, etc.
Sony Ericsson
next prev parent reply other threads:[~2011-11-03 7:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-03 6:10 Folder level Acces in git redhat1981
2011-11-03 7:17 ` Magnus Bäck [this message]
2011-11-03 18:13 ` Jens Lehmann
2011-11-03 19:28 ` Eugene Sajine
2011-11-04 4:21 ` Joshua Jensen
2011-11-04 8:42 ` Jens Lehmann
2011-11-04 15:59 ` Eugene Sajine
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20111103071701.GA22412@jpl.local \
--to=magnus.back@sonyericsson.com \
--cc=git@vger.kernel.org \
--cc=redhat1981@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).