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

Re: [BUG] Out of memory on git log --simplify-by-decoration --first-parent

From
Junio C Hamano <gitster@pobox.com>
Date
Jun 8, 2012, 20:09 UTC
Message-ID
<7vwr3hbm6x.fsf@alter.siamese.dyndns.org>
In-Reply-To
<4FD24330.2030805@lyx.org>
Vincent van Ravesteijn <vfr@lyx.org> writes:
> git dies after calling the following command on the git repo:
>
> $ git log f623ca1c...b9cfa4e9 --simplify-by-decoration --first-parent

I wouldn't be surprised anything random happens when --first-parent is used together with simplify_merges(); the function needs full analysis of all commits in the specified range, and first-parent traversal specifically tells us not to descend into other parents. It might not be a bad idea to forbid this combination when the command line options are parsed.

What information were you trying to get out of the above command?
Previous: Vincent van RavesteijnNext: Vincent van Ravesteijn
Message 2 of 4 in “[BUG] Out of memory on git log --simplify-by-decoration --first-parent”
  1. Vincent van RavesteijnJun 8, 2012
  2. Junio C HamanoJun 8, 2012
  3. Vincent van RavesteijnJun 8, 2012
  4. Junio C HamanoJun 8, 2012

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.