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

Re: [PATCH 0/2] teach am and rebase -q/--quiet

From
Junio C Hamano <gitster@pobox.com>
Date
Jun 13, 2009, 23:05 UTC
Message-ID
<7vk53fvini.fsf@alter.siamese.dyndns.org>
In-Reply-To
<1244924500-27391-1-git-send-email-bebarino@gmail.com>
Stephen Boyd <bebarino@gmail.com> writes:
> I am not sure why "current branch $branch is up to date" and
> "Fast-forwarded $branch to $onto" is echoed to stderr, but I've
> wrapped those in a quiet check because it doesn't seem to be
> an error. Maybe those should be changed to stdout?

There are many valid cases where it makes sense to use stderr for messages that are not errors (e.g. diagnostics, prompts, progress reports, and informational messages that otherwise would clutter machine parsable output meant to go to stdout).

I do not understand why some people seem to think stderr is only for errors. I think we even saw a broken interpretive language environment where the system considers it an error if a program it launched said anything to stderr, instead of correctly diagnosing the exit status from it?

It is a disease.
Previous: Stephen BoydNext: Stephen Boyd
Message 4 of 18 in “teach am and rebase -q/--quiet”
  1. 0/2 teach am and rebase -q/--quietStephen Boyd, Jun 13, 2009
  2. 1/2 am: teach quiet optionStephen Boyd, Jun 13, 2009
  3. 2/2 rebase: teach quiet optionStephen Boyd, Jun 13, 2009
  4. Junio C HamanoJun 13, 2009
  5. Stephen BoydJun 14, 2009
  6. Sverre RabbelierJun 14, 2009
  7. Junio C HamanoJun 13, 2009
  8. Stephen BoydJun 14, 2009
  9. Junio C HamanoJun 14, 2009
  10. 0/3 Teach shell scripts to be quietStephen Boyd, Jun 14, 2009
  11. 1/3 git-sh-setup: introduce say() for quiet optionsStephen Boyd, Jun 14, 2009
  12. 2/3 submodule, repack: migrate to git-sh-setup's say()Stephen Boyd, Jun 14, 2009
  13. 3/3 am, rebase: teach quiet optionStephen Boyd, Jun 14, 2009
  14. Thomas AdamJun 14, 2009
  15. Junio C HamanoJun 15, 2009
  16. Stephen BoydJun 15, 2009
  17. Johannes SixtJun 15, 2009
  18. Stephen BoydJun 15, 2009

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.