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

[RFC/PATCH 0/3] git-gui: Don’t trigger garbage collection warning so easily

From
Jonathan Nieder <jrnieder@gmail.com>
Date
Feb 18, 2010, 14:34 UTC
Message-ID
<20100218143431.GA30486@progeny.tock>

Using git gui from a repository tracking (for example) linux-next, there are almost always enough loose objects to trigger the garbage collection warning. The default threshold for this warning is much more sensitive than the "as many objects as were in v0.99" rule that the command-line tools use, and the result might be considered even more invasive because the user has to hit yes before it starts packing, and it packs more thoroughly than the default gc --auto settings would.

Moreover, in repositories with many loose objects not referenced only by the reflog (like linux-next), the gc does not do any good. Taken together, these things mean that every time a person runs git gui, they get a message asking them to forfeit a long period of time to accomplish nothing.

This problem was reported by Mark Brown at <http://bugs.debian.org/497687>. My first thought was to add a “don’t ask me again” check box to the dialog suggesting repacking, but my Tk fu is not up to it. :(

The next best thing would be to make ‘git gui’ use gc --auto itself. I wonder:

 - Could git gui use git gc?  I understand from commit bc7452f that
   the output of git gc might not be stable enough for git gui to rely
   on, but why not add a --porcelain option whose output is?
 - Should git gui run git gc --auto without asking for permission?
   This is what the command line tools already do; with a GUI one
   could further provide a button to cancel the gc without closing
   the GUI.

This series does the simplest thing I could figure out how to implement: it builds in the heuristic for counting loose objects from builtin-gc.c into git-gui (so it will respect the gc.auto configuration and by default will trigger much less often) and if that heuristic is satisfied, runs gc --auto.

Advice? Am I on the right track here? Any advice for specifying an interface for a --porcelain option to do this the right way?

Jonathan Nieder (3):
  git-gui: factor out too_many_loose_objects routine from hint_gc
  git-gui: Do not hold the user hostage with a full gc at startup
  git-gui: Do not suggest a gc if gc --auto would not do it
 lib/database.tcl |   40 +++++++++++++++++++++++++++++++++++-----
 1 files changed, 35 insertions(+), 5 deletions(-)
Next: Jonathan Nieder
Message 1 of 6 in “git-gui: Don’t trigger garbage collection warning so easily”
  1. 0/3 git-gui: Don’t trigger garbage collection warning so easilyJonathan Nieder, Feb 18, 2010
  2. 1/3 git-gui: factor out too_many_loose_objects routine from hint_gcJonathan Nieder, Feb 18, 2010
  3. 2/3 git-gui: Do not hold the user hostage with a full gc at startupJonathan Nieder, Feb 18, 2010
  4. 3/3 git-gui: Do not suggest a gc if gc --auto would not do itJonathan Nieder, Feb 18, 2010
  5. Jonathan NiederFeb 18, 2010
  6. Johannes SixtFeb 18, 2010

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.