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, 09:57 UTC
Message-ID
<81b0412b0703080157n413de6f6q35ae24e2620df91d@mail.gmail.com>
In-Reply-To
<7vy7m8aytt.fsf@assigned-by-dhcp.cox.net>
On 3/8/07, Junio C Hamano <junkio@cox.net> wrote:
Show 6 quoted lines
> But this is only true if you want to make it really nice.  I
> personally feel that nobody would scream if pushing 1300 refs at
> once (4K pages and MAX_ARG_PAGES at 32 would give 128K for
> **argv and its strings, and one ref's worth of data is two
> 40-digit hex plus refname, roughly 100-byte per ref) is not
> supported and always failed.

I'm not too worried about linux. It wont have any problems even if you supply megabytes of arguments (if someone will really need such lists, he can increase MAX_ARG_PAGES and be done with it).

The proprietary OS' will have the problem, though. And far sooner than 1300 refs (w2k has only 32767 bytes for command line). Besides, don't overestimate peoples readiness to be careful about reference names. I would expect reference names over 100 bytes in length to happen regularly (generated from file names appended with a timestamp, for example).

Maybe provide this hooks with simply formatted list on stdin? I.e.
<old-ref> <new-ref> <ref-name> LF
Previous: Shawn O. PearceNext: Shawn O. Pearce
Message 8 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.