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

Re: [PATCH] git-fetch: print informative messages to stdout, not stderr

From
Junio C Hamano <gitster@pobox.com>
Date
Oct 26, 2007, 21:01 UTC
Message-ID
<7vr6jhwpyc.fsf@gitster.siamese.dyndns.org>
In-Reply-To
<20071026085355.24930.qmail@2c06371a7c3ae6.315fe32.mid.smarden.org>
Gerrit Pape <pape@smarden.org> writes:
> git-fetch writes informations about storing tags and the like to stderr,
> which should only be used for errors.  This patch changes it to use
> stdout instead.

I do not have strong preference but the reason this goes to stderr is because it is considered part of the progress reporting. It is not designed for consumption by scripted callers, and its formatting is subject to change freely, which is what allows the recent "terse fetch" discussion.

Previous: Gerrit Pape
Message 2 of 2 in “git-fetch: print informative messages to stdout, not stderr”
  1. git-fetch: print informative messages to stdout, not stderrGerrit Pape, Oct 26, 2007
  2. Junio C HamanoOct 26, 2007

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.