Implementation bug with cherry-picking multiple commits

From: Dun Peal <dunpealer@gmail.com>
Date: Oct 1, 2010, 16:16 UTC
Message-ID: <AANLkTimhwomGnmCEAyPaGj=fST8zkMO1sTyJ2dxRzWMW@mail.gmail.com>

I tried using the new feature allowing the cherry-picking of multiple commits at the same time:

  $ git cherry-pick foo~100...foo

I got an error that indicates a potential implementation bug:

  error: cannot fork() for commit: Cannot allocate memory

This is a powerful CentOS server with almost 8GB of free RAM at the cherry-pick operation runtime.

Thanks, D

$ 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.