From: Junio C Hamano <gitster@pobox.com>
Date: Wed, 09 Jan 2013 21:49:41 GMT
Subject: Re: [RFC/PATCH] avoid SIGPIPE warnings for aliases
Message-ID: <7vehhu3u2y.fsf@alter.siamese.dyndns.org>
In-Reply-To: <20130109205116.GA24605@sigill.intra.peff.net>

Jeff King <peff@peff.net> writes:

> But we still say "error: ... died of signal 13", because that comes from
> inside wait_or_whine. So it is a separate issue whether or not
> wait_or_whine should be silent on SIGPIPE (we already are on SIGINT and
> SIGQUIT, as of some recent patches).
>
> The upside is that it is noise in this case that we would no longer see.
> The downside is that we may be losing a clue when debugging server
> problems, which do not expect to die from SIGPIPE.  Should it be an
> optional run-command flag?

Do we know if we are upstream of a pager that reads from us through
a pipe (I think we should, especially in a case where we are the one
who processed the "git -p $alias" option)?  Is there any other case
where we would want to ignore child's death by SIGPIPE?  If the
answers are yes and no, then perhaps we can ask pager_in_use() to
decide this?