git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Frans Klaver" <fransklaver@gmail.com>
To: git@vger.kernel.org, 乙酸鋰 <ch3cooli@gmail.com>
Subject: Re: git die message written to stdout?
Date: Wed, 26 Sep 2012 21:11:33 +0200	[thread overview]
Message-ID: <op.wk9bljau0aolir@keputer> (raw)
In-Reply-To: <CAHtLG6T5nHw-47GdRHsXNCeArKy5X5XUmHxLnj50osKoUQa+dQ@mail.gmail.com>

On Wed, 26 Sep 2012 18:01:39 +0200, 乙酸鋰 <ch3cooli@gmail.com> wrote:

> Is git die() messages written to stdout?
> Should it be written to stderr?

As far as I know git die() routines write their output to stderr. Do you  
have an indication that that might not be the case?

Frans


> --
> To unsubscribe from this list: send the line "unsubscribe git" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

      reply	other threads:[~2012-09-26 19:11 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-26 16:01 git die message written to stdout? 乙酸鋰
2012-09-26 19:11 ` Frans Klaver [this message]

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=op.wk9bljau0aolir@keputer \
    --to=fransklaver@gmail.com \
    --cc=ch3cooli@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).