From: "Gonzalo Garramuño" <ggarra@advancedsl.com.ar>
To: git@vger.kernel.org
Subject: Git and securing a repository
Date: Wed, 02 Jan 2008 04:13:57 -0300 [thread overview]
Message-ID: <477B39B5.5010107@advancedsl.com.ar> (raw)
I've been using git for some time and love it. For open source projects
there's clearly nothing currently better.
However, I am now using git for proprietary elements, which in the
future I may need or want to partially restrict access to. The idea
being that at my company some (junior) developers should not be given
access to some elements. That means either that some full git
repository should be password protected or even portions of the same
repository.
Another desirable way to protect elements might be only giving
clone/pull access to a repository (or portion of it) but not permissions
to push in changes.
I have not seen or read much about how git deals with accesses and
permissions. Can anyone point me to some documentation if some or all
of this is possible?
--
Gonzalo Garramuño
ggarra@advancedsl.com.ar
AMD4400 - ASUS48N-E
GeForce7300GT
Xubuntu Gutsy
next reply other threads:[~2008-01-02 6:13 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-02 7:13 Gonzalo Garramuño [this message]
2008-01-02 6:34 ` Git and securing a repository Felipe Balbi
2008-01-02 10:04 ` Gonzalo Garramuño
2008-01-02 9:26 ` David Symonds
2008-01-02 10:39 ` Gonzalo Garramuño
2008-01-02 10:51 ` Jakub Narebski
2008-01-03 3:58 ` Shawn O. Pearce
2008-01-03 4:30 ` Bruno Cesar Ribas
2008-01-03 5:36 ` Gonzalo Garramuño
2008-01-03 4:45 ` Shawn O. Pearce
2008-01-03 6:08 ` Gonzalo Garramuño
2008-01-03 5:19 ` Shawn O. Pearce
2008-01-03 9:11 ` Jakub Narebski
2008-01-03 9:36 ` Junio C Hamano
2008-01-02 19:31 ` Jan Hudec
2008-01-02 19:41 ` Gregory Jefferis
2008-01-02 22:17 ` Linus Torvalds
2008-01-02 16:18 ` Daniel Barkalow
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=477B39B5.5010107@advancedsl.com.ar \
--to=ggarra@advancedsl.com.ar \
--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).