Ondřej Vašík wrote:
> Jim Meyering wrote:
> > Would you mind separating that into a few separate change sets?
> ...
> I hope I will do the rest of patches ( 1 or 2 more
> are still necessary to cover all the issues I found).
Here is the second set of patches.
First one (getdate_4) addresses issu
Ondřej Vašík <[EMAIL PROTECTED]> wrote:
...
> From 4c9db16207b5c76bb85b05ee5853c525372bb80a Mon Sep 17 00:00:00 2001
> From: =?utf-8?q?Ond=C5=99ej=20Va=C5=A1=C3=ADk?= <[EMAIL PROTECTED]>
> Date: Fri, 27 Jun 2008 16:32:28 +0200
> Subject: [PATCH] *lib/getdate.y: Do not ignore specified time zone whe
Ondřej Vašík <[EMAIL PROTECTED]> wrote:
> Jim Meyering wrote:
...
> From 4c9db16207b5c76bb85b05ee5853c525372bb80a Mon Sep 17 00:00:00 2001
> From: =?utf-8?q?Ond=C5=99ej=20Va=C5=A1=C3=ADk?= <[EMAIL PROTECTED]>
> Date: Fri, 27 Jun 2008 16:32:28 +0200
> Subject: [PATCH] *lib/getdate.y: Do not ignore s
Andreas Schwab wrote:
It seems to me that tee should have a SIGPIPE handler which closes the
broken fd and stops trying to write to it, and if ALL outputs have been
closed, exit.
That would not be compatible with POSIX.
In what way?
Also, won't ignoring SIGPIPE cause problems later when tee
Bruno Haible <[EMAIL PROTECTED]> wrote:
> Andreas Schwab wrote:
>> > How about adding an option '-p' to 'tee', that causes it to ignore SIGPIPE
>> > while writing to stdout?
>>
>> Just add a trap '' SIGPIPE before starting tee.
>
> Thanks, this does half of the trick: Each 'tee' invocation then wri
Phillip Susi <[EMAIL PROTECTED]> writes:
> Andreas Schwab wrote:
>>> It seems to me that tee should have a SIGPIPE handler which closes the
>>> broken fd and stops trying to write to it, and if ALL outputs have been
>>> closed, exit.
>>
>> That would not be compatible with POSIX.
>
> In what way?
