git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
* Pointers to setup an internal git repository with access control
@ 2011-08-30 12:01 robert mena
  2011-08-30 12:22 ` Konstantin Khomoutov
  2011-08-30 18:33 ` Magnus Bäck
  0 siblings, 2 replies; 5+ messages in thread
From: robert mena @ 2011-08-30 12:01 UTC (permalink / raw)
  To: git

Hi,

I am trying to migrate from SVN to git and so I am looking for tools
that help me create an interal repository.  I currently use SVN over
HTTPS/Dav using the access.conf to be able to control which uses can
read/write to the repos or given branches.

Ideally I am looking for tools that enable me to do the same with git.

Regards.

^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: Pointers to setup an internal git repository with access control
  2011-08-30 12:01 Pointers to setup an internal git repository with access control robert mena
@ 2011-08-30 12:22 ` Konstantin Khomoutov
  2011-08-30 12:35   ` robert mena
  2011-08-30 18:33 ` Magnus Bäck
  1 sibling, 1 reply; 5+ messages in thread
From: Konstantin Khomoutov @ 2011-08-30 12:22 UTC (permalink / raw)
  To: robert mena; +Cc: git

On Tue, 30 Aug 2011 08:01:44 -0400
robert mena <robert.mena@gmail.com> wrote:

> I am trying to migrate from SVN to git and so I am looking for tools
> that help me create an interal repository.  I currently use SVN over
> HTTPS/Dav using the access.conf to be able to control which uses can
> read/write to the repos or given branches.
> 
> Ideally I am looking for tools that enable me to do the same with git.
Possibly look at smart http protocol [1], [2].

I may be wrong, but this access method cannot be used to implemet
access control with branch-level granularity.  If you really need this,
use gitolite [3].

1. http://progit.org/2010/03/04/smart-http.html
2. http://www.kernel.org/pub/software/scm/git/docs/git-http-backend.html
3. https://github.com/sitaramc/gitolite

^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: Pointers to setup an internal git repository with access control
  2011-08-30 12:22 ` Konstantin Khomoutov
@ 2011-08-30 12:35   ` robert mena
  2011-08-30 12:59     ` Konstantin Khomoutov
  0 siblings, 1 reply; 5+ messages in thread
From: robert mena @ 2011-08-30 12:35 UTC (permalink / raw)
  To: Konstantin Khomoutov; +Cc: git

Hi,

Thanks for the reply.  I'll take a look.

I don't have to use https+dav, it can be ssh as long as it is
encrypted and I have some sort of access control.  The branches item
is to be able to control who can merge/commit things back to, for
example, the trunk or whatever I call the "live" branch.

This way the devs can do what they want but the final merge to the
"live" branch would be done after the Q&A approves.

On Tue, Aug 30, 2011 at 8:22 AM, Konstantin Khomoutov
<flatworm@users.sourceforge.net> wrote:
> On Tue, 30 Aug 2011 08:01:44 -0400
> robert mena <robert.mena@gmail.com> wrote:
>
>> I am trying to migrate from SVN to git and so I am looking for tools
>> that help me create an interal repository.  I currently use SVN over
>> HTTPS/Dav using the access.conf to be able to control which uses can
>> read/write to the repos or given branches.
>>
>> Ideally I am looking for tools that enable me to do the same with git.
> Possibly look at smart http protocol [1], [2].
>
> I may be wrong, but this access method cannot be used to implemet
> access control with branch-level granularity.  If you really need this,
> use gitolite [3].
>
> 1. http://progit.org/2010/03/04/smart-http.html
> 2. http://www.kernel.org/pub/software/scm/git/docs/git-http-backend.html
> 3. https://github.com/sitaramc/gitolite
>

^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: Pointers to setup an internal git repository with access control
  2011-08-30 12:35   ` robert mena
@ 2011-08-30 12:59     ` Konstantin Khomoutov
  0 siblings, 0 replies; 5+ messages in thread
From: Konstantin Khomoutov @ 2011-08-30 12:59 UTC (permalink / raw)
  To: robert mena; +Cc: Konstantin Khomoutov, git

On Tue, 30 Aug 2011 08:35:22 -0400
robert mena <robert.mena@gmail.com> wrote:

[...]
> I don't have to use https+dav, it can be ssh as long as it is
> encrypted and I have some sort of access control.  The branches item
> is to be able to control who can merge/commit things back to, for
> example, the trunk or whatever I call the "live" branch.
> 
> This way the devs can do what they want but the final merge to the
> "live" branch would be done after the Q&A approves.
Go for gitolite then.

^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: Pointers to setup an internal git repository with access control
  2011-08-30 12:01 Pointers to setup an internal git repository with access control robert mena
  2011-08-30 12:22 ` Konstantin Khomoutov
@ 2011-08-30 18:33 ` Magnus Bäck
  1 sibling, 0 replies; 5+ messages in thread
From: Magnus Bäck @ 2011-08-30 18:33 UTC (permalink / raw)
  To: robert mena; +Cc: git

On Tuesday, August 30, 2011 at 14:01 CEST,
     robert mena <robert.mena@gmail.com> wrote:

> I am trying to migrate from SVN to git and so I am looking for tools
> that help me create an interal repository.  I currently use SVN over
> HTTPS/Dav using the access.conf to be able to control which uses can
> read/write to the repos or given branches.
> 
> Ideally I am looking for tools that enable me to do the same with git.

Gerrit Code Review (http://code.google.com/p/gerrit/) provides
branch-level ACLs for both reading and writing.

-- 
Magnus Bäck                   Opinions are my own and do not necessarily
SW Configuration Manager      represent the ones of my employer, etc.
Sony Ericsson

^ permalink raw reply	[flat|nested] 5+ messages in thread

end of thread, other threads:[~2011-08-30 18:33 UTC | newest]

Thread overview: 5+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2011-08-30 12:01 Pointers to setup an internal git repository with access control robert mena
2011-08-30 12:22 ` Konstantin Khomoutov
2011-08-30 12:35   ` robert mena
2011-08-30 12:59     ` Konstantin Khomoutov
2011-08-30 18:33 ` Magnus Bäck

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).