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

Re: final git bisect step leads to: "fatal: you want to use way too much memory"

From
MTMarkus Trippelsdorf <markus@trippelsdorf.de>
Date
Jun 16, 2016, 13:29 UTC
Message-ID
<20160616132952.GC314@x4>
In-Reply-To
<20160616125326.GA314@x4>
On 2016.06.16 at 14:53 +0200, Markus Trippelsdorf wrote:
Show 5 quoted lines
> markus@x4 gcc % git bisect good
> f216419e5c4c41df70dbe00a6ea1faea46484dc8 is the first bad commit
> commit f216419e5c4c41df70dbe00a6ea1faea46484dc8
> fatal: you want to use way too much memory
> markus@x4 gcc % 
The issue started with:
commit fe37a9c586a65943e1bca327a1bbe1ca4a3d3023
Author: Junio C Hamano <gitster@pobox.com>
Date:   Tue Mar 29 16:05:39 2016 -0700
    pretty: allow tweaking tabwidth in --expand-tabs
-- 
Markus
Previous: Markus TrippelsdorfNext: Jeff King
Message 3 of 8 in “final git bisect step leads to: "fatal: you want to use way too much memory"”
  1. Markus TrippelsdorfJun 16, 2016
  2. Markus TrippelsdorfJun 16, 2016
  3. Markus TrippelsdorfJun 16, 2016
  4. Jeff KingJun 16, 2016
  5. Junio C HamanoJun 16, 2016
  6. bisect: always call setup_revisions after init_revisionsJeff King, Jun 16, 2016
  7. Junio C HamanoJun 17, 2016
  8. Jeff KingJun 17, 2016

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.