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

Re: [RFC] Using sticky directories to control access to branches.

From
Junio C Hamano <junkio@cox.net>
Date
Dec 2, 2005, 01:13 UTC
Message-ID
<7vwtio9u8f.fsf@assigned-by-dhcp.cox.net>
In-Reply-To
<20051201154222.GB18993@hpsvcnb.fc.hp.com>
Carl Baldwin <cnb@fc.hp.com> writes:
> I have tweaked the script a little.  I thought I'd send to the list in
> case anyone was following this.  If not, then safely ignore this.

It _might_ make sense to have a contrib/examples subdirectory in git.git project and keep a collection of examples like this.

Anybody else interested?
Previous: Carl BaldwinNext: Andreas Ericsson
Message 6 of 8 in “[RFC] Using sticky directories to control access to branches.”
  1. Carl BaldwinNov 17, 2005
  2. Junio C HamanoNov 18, 2005
  3. Carl BaldwinNov 21, 2005
  4. Junio C HamanoNov 21, 2005
  5. Carl BaldwinDec 1, 2005
  6. Junio C HamanoDec 2, 2005
  7. Andreas EricssonDec 2, 2005
  8. Junio C HamanoDec 2, 2005

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.