All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Boyd Stephen Smith Jr." <bss03@volumehost.net>
To: git@vger.kernel.org
Cc: Tim Olsen <tim@brooklynpenguin.com>
Subject: Re: fatal output from git-show really wants a terminal
Date: Wed, 10 Dec 2008 10:10:14 -0600	[thread overview]
Message-ID: <200812101010.14868.bss03@volumehost.net> (raw)
In-Reply-To: <ghop5d$qud$1@ger.gmane.org>

[-- Attachment #1: Type: text/plain, Size: 701 bytes --]

On Wednesday 2008 December 10 10:01:49 you wrote:
>It appears that when outputting a fatal error, git-show will choose
>stdout over stderr if stdout is a terminal and stderr is not.  How do I
>redirect the error but still allow stdout to be displayed?

Gah, I think that's really bad behavior. Anyway, something like:
git show 12345 2>/dev/null | cat
should work.  Neither stdout nor stderr will be a terminal, but stdout will be 
displayed to your terminal.
-- 
Boyd Stephen Smith Jr.                     ,= ,-_-. =. 
bss03@volumehost.net                      ((_/)o o(\_))
ICQ: 514984 YM/AIM: DaTwinkDaddy           `-'(. .)`-' 
http://iguanasuicide.org/                      \_/     

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 197 bytes --]

  reply	other threads:[~2008-12-10 16:11 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-10 16:01 fatal output from git-show really wants a terminal Tim Olsen
2008-12-10 16:10 ` Boyd Stephen Smith Jr. [this message]
2008-12-10 19:46 ` Johannes Sixt
2008-12-10 20:10   ` Tim Olsen
2008-12-10 22:24   ` Boyd Stephen Smith Jr.
     [not found]     ` <alpine.DEB.1.00.0812111015140.18321@eeepc-johanness>
2008-12-11 16:51       ` Boyd Stephen Smith Jr.
2008-12-11 21:55         ` Jeff King
2008-12-11 22:45           ` Boyd Stephen Smith Jr.
2008-12-11 22:59             ` Jeff King
2008-12-11 23:03             ` Junio C Hamano
2008-12-15  8:15               ` Junio C Hamano
2008-12-15  8:23                 ` Junio C Hamano
2008-12-15  8:25                 ` Jeff King

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=200812101010.14868.bss03@volumehost.net \
    --to=bss03@volumehost.net \
    --cc=git@vger.kernel.org \
    --cc=tim@brooklynpenguin.com \
    /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.