git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: Pointers to setup an internal git repository with access control

From
KKKonstantin Khomoutov <flatworm@users.sourceforge.net>
Date
Aug 30, 2011, 12:59 UTC
Message-ID
<20110830165937.188baae9.kostix@domain007.com>
In-Reply-To
<CAAZ43xYhFQzBVmjfnvRoboNPQ1OLtyq57=0ZL3B6p+dRWnJZ-g@mail.gmail.com>

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

[...]
Show 7 quoted lines
> 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.
Previous: robert menaNext: Magnus Bäck
Message 4 of 5 in “Pointers to setup an internal git repository with access control”
  1. robert menaAug 30, 2011
  2. Konstantin KhomoutovAug 30, 2011
  3. robert menaAug 30, 2011
  4. Konstantin KhomoutovAug 30, 2011
  5. Magnus BäckAug 30, 2011

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.