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

Re: Mark remote `gc --auto` error messages

From
Junio C Hamano <gitster@pobox.com>
Date
Jun 2, 2016, 21:59 UTC
Message-ID
<xmqqmvn3s148.fsf@gitster.mtv.corp.google.com>
In-Reply-To
<20160602214834.GB13356@sigill.intra.peff.net>
Jeff King <peff@peff.net> writes:
> So the greater question is not "should this output be marked" but
> "should auto-gc data go over the sideband so that all clients see it
> (and any server-side stderr does not)". And I think the answer is
> probably yes. And that fixes the "remote: " thing as a side effect.

Thanks for stating this a lot more clearly than I could, and I agree that sending this to the other side regardless of the protocol is the right thing. I somehow doubt that server operators would check Apache logs to decide when to do a proper GC, so I do not consider it a true loss ;-)

Previous: Jeff KingNext: Jeff King
Message 6 of 9 in “Mark remote `gc --auto` error messages”
  1. Lukas FleischerJun 2, 2016
  2. Junio C HamanoJun 2, 2016
  3. Lukas FleischerJun 2, 2016
  4. Junio C HamanoJun 2, 2016
  5. Jeff KingJun 2, 2016
  6. Junio C HamanoJun 2, 2016
  7. Jeff KingJun 2, 2016
  8. Jeff KingJun 2, 2016
  9. receive-pack: send auto-gc output over sideband 2Lukas Fleischer, Jun 5, 2016

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.