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

Re: git gc and kernel.org

From
Junio C Hamano <gitster@pobox.com>
Date
Oct 21, 2009, 07:39 UTC
Message-ID
<7vaazl8acd.fsf@alter.siamese.dyndns.org>
In-Reply-To
<7vzl7l8b1y.fsf@alter.siamese.dyndns.org>
Junio C Hamano <gitster@pobox.com> writes:
Show 13 quoted lines
> Johannes Sixt <j.sixt@viscovery.net> writes:
>
>> Junio C Hamano schrieb:
>>> +		if (auto_gc) {
>>> +			const char *argv_gc_auto[] = { "gc", "--auto", NULL };
>>> +			run_command_v_opt(argv_gc_auto, RUN_GIT_CMD);
>>
>> Am I correct that this will produce progress output? If git-daemon runs
>> receive-pack, then this output will go to the syslog. Do we care?
>
> We do, and we don't want that.  Thanks for spotting.
>
> Would adding "--quiet" to the mix be enough?

Actually I don't know. This originally came from "we _could_ add gc and update-server-info to hundreds of post-receive hooks, but any repository hosting site that holds many central repositories will exactly have the same issue, so why not do this internally", so it may make sense to do exactly the same thing as what we do to the output from hooks. What do we do to them now? stdout-to-stderr?

Previous: Junio C HamanoNext: Johannes Sixt
Message 12 of 18 in “git gc and kernel.org”
  1. H. Peter AnvinOct 20, 2009
  2. Junio C HamanoOct 20, 2009
  3. H. Peter AnvinOct 20, 2009
  4. Johan HerlandOct 20, 2009
  5. Nicolas PitreOct 20, 2009
  6. Junio C HamanoOct 20, 2009
  7. Nicolas PitreOct 20, 2009
  8. receive-pack: run "gc --auto" and optionally "update-server-info"Junio C Hamano, Oct 20, 2009
  9. Nicolas PitreOct 21, 2009
  10. Johannes SixtOct 21, 2009
  11. Junio C HamanoOct 21, 2009
  12. Junio C HamanoOct 21, 2009
  13. Johannes SixtOct 21, 2009
  14. Jan KrügerOct 21, 2009
  15. 1/2 gc --auto --quiet: make the notice a bit less verboaseJunio C Hamano, Oct 21, 2009
  16. 2/2 receive-pack: run "gc --auto --quiet " and optionally "update-server-info"Junio C Hamano, Oct 21, 2009
  17. Mikael MagnussonOct 20, 2009
  18. H. Peter AnvinOct 21, 2009

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.