From: "Carlos Martín Nieto" <cmn@elego.de>
To: Grant <emailgrant@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: Does git have "Path-Based Authorization"?
Date: Sat, 01 Oct 2011 02:05:02 +0200 [thread overview]
Message-ID: <1317427503.4331.37.camel@centaur.lab.cmartin.tk> (raw)
In-Reply-To: <CAN0CFw0QXkNSF8+qGu+pCrv5dgy1OEvtq-53f23GRd4RrZ1GcQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1187 bytes --]
On Fri, 2011-09-30 at 16:43 -0700, Grant wrote:
> Hello, I'm trying to decide between git and subversion. Subversion
> has "Path-Based Authorization" so I can give a developer access to
> only specific files instead of everything. Does git have something
> similar?
Git's model does not allow the same type "Path-Based Authorization" that
Subversion uses, because git uses secure hash sums to make sure that
people don't try to sneak changes into a pull request or merge, and you
can't selectively download parts of the tree because then you couldn't
check that one of your remotes isn't trying to lie to you.
You can do something that is (or can be) similar with git and
gitolite[0] so a developer (or set of developers) only has access to a
particular set of branches. Depending on what exactly you're trying to
do, this can be more or less complicated to set up. If you only want a
set of developers to access the subdirectory
clients/importantsecretclient, then you create that directory only in
the branch or branches that developer can read. There are many examples
int he gitolite wiki.
[0] https://github.com/sitaramc/gitolite/wiki/
HTH
cmn
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 490 bytes --]
next prev parent reply other threads:[~2011-10-01 0:05 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-30 23:43 Does git have "Path-Based Authorization"? Grant
2011-10-01 0:05 ` Carlos Martín Nieto [this message]
2011-10-01 1:31 ` Grant
2011-10-01 1:34 ` Nguyen Thai Ngoc Duy
2011-10-01 1:43 ` Grant
2011-10-01 2:09 ` david
2011-10-01 13:06 ` Jakub Narebski
2011-10-02 0:00 ` Grant
2011-10-02 1:27 ` Sitaram Chamarty
2011-10-02 2:53 ` Grant
2011-10-02 3:24 ` Nguyen Thai Ngoc Duy
2011-10-02 3:34 ` Grant
2011-10-02 6:38 ` Andreas Krey
2011-10-02 6:43 ` Frans Klaver
2011-10-02 14:50 ` Enrico Weigelt
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=1317427503.4331.37.camel@centaur.lab.cmartin.tk \
--to=cmn@elego.de \
--cc=emailgrant@gmail.com \
--cc=git@vger.kernel.org \
/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).