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

Re: Why is --graph --max-count=n so much slower than --graph HEAD~n..?

From
Junio C Hamano <gitster@pobox.com>
Date
May 20, 2014, 22:50 UTC
Message-ID
<xmqq61l0rrng.fsf@gitster.dls.corp.google.com>
In-Reply-To
<vnkwd2f8ayea.fsf@mitchelh-linux.qualcomm.com>
Mitchel Humpherys <mitch.special@gmail.com> writes:
> I've noticed that --max-count doesn't seem to speed up `git log --graph'
> computation time.

AFAIK, --graph wants to compute the whole history and the max-count only affects the output phase after --graph does its computation.

Besides, "log --max-count=n" and "log HEAD~n.." compute completely different things, so the comparison is apples and oranges.

Previous: Mitchel HumpherysNext: Mitchel Humpherys
Message 2 of 4 in “Why is --graph --max-count=n so much slower than --graph HEAD~n..?”
  1. Mitchel HumpherysMay 20, 2014
  2. Junio C HamanoMay 20, 2014
  3. Mitchel HumpherysMay 21, 2014
  4. Junio C HamanoMay 21, 2014

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.