All of lore.kernel.org
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Stephen Boyd <bebarino@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH 0/2] teach am and rebase -q/--quiet
Date: Sat, 13 Jun 2009 16:05:53 -0700	[thread overview]
Message-ID: <7vk53fvini.fsf@alter.siamese.dyndns.org> (raw)
In-Reply-To: <1244924500-27391-1-git-send-email-bebarino@gmail.com> (Stephen Boyd's message of "Sat\, 13 Jun 2009 13\:21\:38 -0700")

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.

  parent reply	other threads:[~2009-06-13 23:06 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-13 20:21 [PATCH 0/2] teach am and rebase -q/--quiet Stephen Boyd
2009-06-13 20:21 ` [PATCH 1/2] am: teach quiet option Stephen Boyd
2009-06-13 20:21   ` [PATCH 2/2] rebase: " Stephen Boyd
2009-06-13 23:05 ` Junio C Hamano [this message]
2009-06-14  7:07   ` [PATCH 0/2] teach am and rebase -q/--quiet Stephen Boyd
2009-06-14  8:27   ` Sverre Rabbelier
2009-06-13 23:07 ` Junio C Hamano
2009-06-14  7:16   ` Stephen Boyd
2009-06-14  8:24     ` Junio C Hamano
2009-06-14 23:16 ` [PATCHv2 0/3] Teach shell scripts to be quiet Stephen Boyd
2009-06-14 23:16   ` [PATCHv2 1/3] git-sh-setup: introduce say() for quiet options Stephen Boyd
2009-06-14 23:16     ` [PATCHv2 2/3] submodule, repack: migrate to git-sh-setup's say() Stephen Boyd
2009-06-14 23:16       ` [PATCHv2 3/3] am, rebase: teach quiet option Stephen Boyd
2009-06-14 23:21     ` [PATCHv2 1/3] git-sh-setup: introduce say() for quiet options Thomas Adam
2009-06-15  4:23       ` Junio C Hamano
2009-06-15  6:15         ` Stephen Boyd
2009-06-15  6:25     ` Johannes Sixt
2009-06-15  6:33       ` Stephen Boyd

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=7vk53fvini.fsf@alter.siamese.dyndns.org \
    --to=gitster@pobox.com \
    --cc=bebarino@gmail.com \
    --cc=git@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.