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

Re: Restricting access to a branch

From
Junio C Hamano <gitster@pobox.com>
Date
May 22, 2008, 00:17 UTC
Message-ID
<7vhccrxkdm.fsf@gitster.siamese.dyndns.org>
In-Reply-To
<20080521163616.31fad56f@extreme>
Stephen Hemminger <shemminger@vyatta.com> writes:
Show 5 quoted lines
> Is there some standard way to freeze a branch and not allow anymore changes to
> be pushed?
>
> Yes, I know it is possible by playing with hook files, but that doesn't seem
> very admin friendly.
If you do not want to use hooks, then the answer is no.  Sorry.
Previous: Stephen HemmingerNext: Linus Torvalds
Message 2 of 5 in “Restricting access to a branch”
  1. Stephen HemmingerMay 21, 2008
  2. Junio C HamanoMay 22, 2008
  3. Linus TorvaldsMay 22, 2008
  4. Junio C HamanoMay 22, 2008
  5. Jakub NarebskiMay 22, 2008

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.