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
Martin Langhoff <martin.langhoff@gmail.com>
Date
May 25, 2011, 17:17 UTC
Message-ID
<BANLkTikoqxRBMQvKRsJ0-vNd+cW5k-jQWw@mail.gmail.com>
In-Reply-To
<m2pqn667f9.fsf@igel.home>
On Wed, May 25, 2011 at 1:01 PM, Andreas Schwab <schwab@linux-m68k.org> wrote:
> You can start gitk with --max-count=N

Or --since=2.weeks.ago. Of course I can -- and sometimes do. But gitk defaults to OOMing my box if I forget to do so on a large repo.

> and if you need more commits you
> can edit the current view to increase that number.  No need to restart
> gitk.

Ah, that's news to me! I just tried it and it's... awkward. In fact, the dialog box seems to be missing an 'apply' button.

m
-- 
 martin.langhoff@gmail.com
 martin@laptop.org -- Software Architect - OLPC
 - ask interesting questions
 - don't get distracted with shiny stuff  - working code first
 - http://wiki.laptop.org/go/User:Martinlanghoff
Previous: Andreas SchwabNext: Jeff King
Message 3 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.