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

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

From
Lukas Fleischer <lfleischer@lfos.de>
Date
Jun 2, 2016, 20:06 UTC
Message-ID
<146489800609.1944.4398103814754920753@typhoon.lan>
In-Reply-To
<xmqqinxrtmgi.fsf@gitster.mtv.corp.google.com>
On Thu, 02 Jun 2016 at 21:33:33, Junio C Hamano wrote:
Show 11 quoted lines
> Lukas Fleischer <lfleischer@lfos.de> writes:
> 
> > When running `git push`, it might occur that error messages are
> > transferred from the server to the client. While most messages (those
> > explicitly sent on sideband 2) are prefixed with "remote:", it seems
> > that error messages printed during the automatic householding performed
> > by git-gc(1) are displayed without any additional decoration. Thus, such
> > messages can easily be misinterpreted as git-gc failing locally, see [1]
> > for an actual example of where that happened.
> 
> Sounds like a sensible goal to me.

What exactly are you referring to (you only quoted the introduction)? Do you think we should fix the git-gc issue but keep the general behavior of printing messages unaltered? Do you think it would be worthwhile to make server messages distinguishable in general?

Previous: Junio C HamanoNext: Junio C Hamano
Message 3 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.