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

Re: How to do with access control per repo with a smart http git server?

From
ILIlari Liusvaara <ilari.liusvaara@elisanet.fi>
Date
Nov 24, 2010, 06:08 UTC
Message-ID
<20101124060813.GA12949@LK-Perkele-V2.elisa-laajakaista.fi>
In-Reply-To
<loom.20101124T060650-817@post.gmane.org>
On Wed, Nov 24, 2010 at 05:07:46AM +0000, Chunlin Zhang wrote:
Show 6 quoted lines
> Ilari Liusvaara <ilari.liusvaara <at> elisanet.fi> writes:
> 
> > Easiest way to do it is via Gitolite.
> 
> I notice that:"gitolite depends heavily on ssh pubkey (passwordless) access" (
> https://github.com/sitaramc/gitolite/blob/pu/doc/1-INSTALL.mkd )
 
See http://github.com/sitaramc/gitolite/blob/pu/doc/http-backend.mkd
-Ilari
Previous: Chunlin ZhangNext: Chunlin Zhang
Message 4 of 9 in “How to do with access control per repo with a smart http git server?”
  1. Chunlin ZhangNov 24, 2010
  2. Ilari LiusvaaraNov 24, 2010
  3. Chunlin ZhangNov 24, 2010
  4. Ilari LiusvaaraNov 24, 2010
  5. Chunlin ZhangNov 24, 2010
  6. Chunlin ZhangNov 24, 2010
  7. Sverre RabbelierNov 25, 2010
  8. Chunlin ZhangNov 26, 2010
  9. Chunlin ZhangNov 29, 2010

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.