Re: [Quilt-dev] [patch 2/8]

[John Vandenberg]

On 9/14/05, address@hidden <address@hidden> wrote:
> Unless compiled specially just to avoid it, bash gives an occasional
> disconcerting (but spurious) warning when a process at the receiving
> side of a shell pipe closes before the sender has flushed all of its
> data.  `quilt refresh' is particularly prone.
> 
> This patch simply redirects stderr to /dev/null in the one instance
> that seems to be the root of the problem, and thus saves the bother
> of recompiling bash.

Gary,

I haven't noticed this problem on OS X 10.3.2, using bash 2.05b.0(1). 
If I understand correctly, the following simple case should
demonstrate the problem?

$ (echo foo; i=1; for ((i = 0; i < 100; i++)); do sleep 1; done) | awk
'{ exit }'

If not, could you provide a more complicated case that does cause
report the error, as I would like to see the problem here, or know
what is different.

If there is such a fundamental problem with bash on 10.4.2, a
configure test to reject that build of bash would be a simpler fix.
--
John