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

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

From
MCMarco Costalba <mcostalba@gmail.com>
Date
Dec 2, 2006, 13:20 UTC
Message-ID
<e5bfff550612020520w3ad48a09xfdde63b9050a75cf@mail.gmail.com>
In-Reply-To
<20061111121625.8988.45195.stgit@localhost>
On 11/11/06, Karl Hasselström <kha@treskal.com> wrote:
> Printing progress messages to stdout causes them to get mixed up with
> the actual output of the program. Using stderr is much better, since
> the user can then redirect the two components separately.
>
This patch breaks qgit.

GUI interface to stgit pop and push commands is broken because a command that prints to stderr is considered a failing one by qgit.

I would kindly ask you to:

1 - Revert the patch. That would be the best. You can use a prefix to printed message instead, see git pull, something like 'stg: bla bla bla' . In any case, IMHO, using stderr for normal activity logging does not sound like a great idea in general.

2 - At least add a '-v' '--verbose' option that defaults to quiet so to not break back compatibility.

Thanks Marco

P.S: I cannot change the stderr == 'something has gone wrong' behaviour because the interface to git commands works with this, and, BTW, _all_ the git commands respect the behaviour stderr == empty ->

Previous: Karl HasselströmNext: Catalin Marinas
Message 2 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.