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

Re: [PATCH] Split sample update hook into post-receive hook

From
Alex Riesen <raa.lkml@gmail.com>
Date
Mar 8, 2007, 08:26 UTC
Message-ID
<81b0412b0703080026v6f3990c3x2cefca661b64e00d@mail.gmail.com>
In-Reply-To
<20070308041618.GA29744@spearce.org>
On 3/8/07, Shawn O. Pearce <spearce@spearce.org> wrote:
> +# Called by git-receive-pack with arguments:
> +#    (refname sha1-old sha1-new)+
>  #
What do you do if this breaks because of too many refs passed?
Previous: Shawn O. PearceNext: Shawn O. Pearce
Message 2 of 10 in “Split sample update hook into post-receive hook”
  1. Split sample update hook into post-receive hookShawn O. Pearce, Mar 8, 2007
  2. Alex RiesenMar 8, 2007
  3. Shawn O. PearceMar 8, 2007
  4. Junio C HamanoMar 8, 2007
  5. Shawn O. PearceMar 8, 2007
  6. Sergey VlasovMar 8, 2007
  7. Shawn O. PearceMar 10, 2007
  8. Alex RiesenMar 8, 2007
  9. Shawn O. PearceMar 8, 2007
  10. Alex RiesenMar 8, 2007

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.