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

Re: [PATCH] Print progress message to stderr, not stdout

From
CMCatalin Marinas <catalin.marinas@gmail.com>
Date
Dec 5, 2006, 09:06 UTC
Message-ID
<b0943d9e0612050106k1081813ds98aec9272174a9ae@mail.gmail.com>
In-Reply-To
<Pine.LNX.4.63.0612050841160.28348@wbgn013.biozentrum.uni-wuerzburg.de>
On 05/12/06, Johannes Schindelin <Johannes.Schindelin@gmx.de> wrote:
Show 5 quoted lines
> On Mon, 4 Dec 2006, Catalin Marinas wrote:
> > I'll first move the message back to stdout.
>
> In other parts of git, the progress message is only printed if output goes
> to a tty. Why not do the same?
Thanks for the hint. This seems to me like the easiest solution.
Previous: Karl Hasselström
Message 10 of 10 in “Print progress message to stderr, not stdout”
  1. Print progress message to stderr, not stdoutKarl Hasselström, Nov 11, 2006
  2. Marco CostalbaDec 2, 2006
  3. Catalin MarinasDec 4, 2006
  4. Karl HasselströmDec 4, 2006
  5. Marco CostalbaDec 4, 2006
  6. Catalin MarinasDec 4, 2006
  7. Marco CostalbaDec 5, 2006
  8. Johannes SchindelinDec 5, 2006
  9. Karl HasselströmDec 5, 2006
  10. Catalin MarinasDec 5, 2006

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.