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

Re: Setting up Password protected repositories?

From
JFJ. Bruce Fields <bfields@fieldses.org>
Date
Sep 17, 2006, 16:43 UTC
Message-ID
<20060917164347.GA21710@fieldses.org>
In-Reply-To
<E1GOzP9-0001Fn-G8@jdl.com>
On Sun, Sep 17, 2006 at 11:22:03AM -0500, Jon Loeliger wrote:
Show 8 quoted lines
> So, like, the other day Shawn Pearce mumbled:
> > Access is controlled by standard UNIX user/group read/write access
> > and ACLs if your OS/filesystem support them.  You can also control
> > pushing with an update hook.
> 
> OK.  I seem to recall a recipe down this line somwhere...  Is there
> a current "Best Practices" write up somewhere with these details
> outlined in it?

There's a few sentences in Documentation/cvs-migration.txt, and a little more in Documentation/howto/update-hook-example.txt

--b.
Previous: Jon Loeliger
Message 7 of 7 in “Setting up Password protected repositories?”
  1. Jon LoeligerSep 17, 2006
  2. Junio C HamanoSep 17, 2006
  3. Jon LoeligerSep 17, 2006
  4. Junio C HamanoSep 17, 2006
  5. Shawn PearceSep 17, 2006
  6. Jon LoeligerSep 17, 2006
  7. J. Bruce FieldsSep 17, 2006

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.