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 4, 2006, 22:13 UTC
Message-ID
<b0943d9e0612041413p4f303176x3d0fa95afd1c4a1@mail.gmail.com>
In-Reply-To
<e5bfff550612041034g727a1bebg464f7c523c0fac7f@mail.gmail.com>
On 04/12/06, Marco Costalba <mcostalba@gmail.com> wrote:
Show 10 quoted lines
> On 12/4/06, Karl Hasselström <kha@treskal.com> wrote:
> > I introduced this since I wanted to divert the output to a file, and
> > the progress message had no business being written to that file. But a
> > command line option to suppress progress messages would work just as
> > well if that's what git does.
>
> If you don't mind I would prefer a command line option to _enable_
> progress messages, something like -v or --verbose so to keep back
> compatibility with current versions of tools that do not expect stderr
> messages.

I'll first move the message back to stdout. Does qgit rely on the StGIT output to have a certain format/information? Does the progress message affect it in any way?

I consider many of the other messages to be progress messages (like "pushing... done") and I haven't differentiated between them until Karl's patch. For commands like diff or status, you expect the command to check the working copy anyway and it doesn't output this specific message.

The best would probably be to add a "verbose" config option to enable this message (and maybe a command line option later but this means modifying all the commands to accept this option). I'll try to push this change tomorrow (together with moving from stgitrc to gitconfig).

Previous: Marco CostalbaNext: Marco Costalba
Message 6 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.