Tim Rühsen writes:
> Looks like commit dd5c549f6af8e1143e1a6ef66725eea4bcd9ad50 broke it.
>
> Sadly, the test suite doesn't catch it.
"Wajda, Piotr" writes:
> Patch sent, should be good now.
Does the patch include a test in the test suite to catch this
Patch sent, should be good now.
Piotr
On 08/11/16 22:29, Tim Rühsen wrote:
On Dienstag, 8. November 2016 15:26:14 CET Dale R. Worley wrote:
I've been getting a script working, and as part of it, it appears that
-o does not work correctly. Specifically -o is supposed to send all
"messages" to
Yeah, I'll look into it.
Piotr
On 08/11/16 22:29, Tim Rühsen wrote:
On Dienstag, 8. November 2016 15:26:14 CET Dale R. Worley wrote:
I've been getting a script working, and as part of it, it appears that
-o does not work correctly. Specifically -o is supposed to send all
"messages" to a
On Dienstag, 8. November 2016 15:26:14 CET Dale R. Worley wrote:
> I've been getting a script working, and as part of it, it appears that
> -o does not work correctly. Specifically -o is supposed to send all
> "messages" to a specified log file rather than stderr. But what I see
> is that no
I've been getting a script working, and as part of it, it appears that
-o does not work correctly. Specifically -o is supposed to send all
"messages" to a specified log file rather than stderr. But what I see
is that no messages are sent to the log file.
The command in question is:
wget