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

Re: gitk normal use on linux repo and severe memory pressure

From
Andreas Schwab <schwab@linux-m68k.org>
Date
May 25, 2011, 17:01 UTC
Message-ID
<m2pqn667f9.fsf@igel.home>
In-Reply-To
<BANLkTinrj2AOCMMWazf2F4eKy7Sy56K0vg@mail.gmail.com>
Martin Langhoff <martin.langhoff@gmail.com> writes:
> I am tempted to set a global config option limiting gitk to a couple
> thousand commits, but it's not really the right solution. If I am
> trawling older history, I'll hit the limit and have to close gitk and
> reopen overriding the parameter.

You can start gitk with --max-count=N and if you need more commits you can edit the current view to increase that number. No need to restart gitk.

Andreas.
-- 
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 58CA 54C7 6D53 942B 1756  01D3 44D5 214B 8276 4ED5
"And now for something completely different."
Previous: Martin LanghoffNext: Martin Langhoff
Message 2 of 4 in “gitk normal use on linux repo and severe memory pressure”
  1. Martin LanghoffMay 25, 2011
  2. Andreas SchwabMay 25, 2011
  3. Martin LanghoffMay 25, 2011
  4. Jeff KingMay 25, 2011

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.