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

Re: [PATCH] Introduce gc.autowarnonly config option

From
Junio C Hamano <gitster@pobox.com>
Date
Mar 9, 2012, 19:35 UTC
Message-ID
<7veht15zz8.fsf@alter.siamese.dyndns.org>
In-Reply-To
<CAGdFq_g=+A7q7_ZkUYG6LZ+ehLBtMY+s+nJxhp4FVhUQ4Zo_rA@mail.gmail.com>
Sverre Rabbelier <srabbelier@gmail.com> writes:
Show 6 quoted lines
> On Sat, Nov 5, 2011 at 08:39, Fernando Vezzosi <buccia@repnz.net> wrote:
>> When `git gc --auto` would detect need for garbage collection to run, it
>> would just run. With this patch, enabling gc.autowarnonly will instead
>> make it just emit a warning.
>
> Does anyone know what happened to this patch?

If I recall correctly, it was pointed out that people who would get annoyed by unexpected triggering of an auto gc would get annoyed by constant nagging by this warning until they reach the point that they can stop and run gc themselves, and the patch was never updated to take that issue into account.

Previous: Sverre Rabbelier
Message 9 of 9 in “Introduce gc.autowarnonly config option”
  1. Introduce gc.autowarnonly config optionFernando Vezzosi, Nov 5, 2011
  2. 2/1 gc --auto: warn gc will soon run, give users a chance to run manuallyFernando Vezzosi, Nov 5, 2011
  3. Nguyen Thai Ngoc DuyNov 6, 2011
  4. 2/1 gc --auto: warn gc will soon run, give users a chance to run manuallyFernando Vezzosi, Nov 5, 2011
  5. Junio C HamanoNov 6, 2011
  6. Sverre RabbelierNov 5, 2011
  7. Jay SoffianNov 7, 2011
  8. Sverre RabbelierMar 9, 2012
  9. Junio C HamanoMar 9, 2012

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.