[Bug 12566] ash: read with -t 0 does not return failure if nothing is read after a successful first read

[bugzilla at busybox.net]

https://bugs.busybox.net/show_bug.cgi?id=12566

--- Comment #1 from Geoff Winkless <busybox at ukku.uk> ---
And immediately after I hit "send" I realised that the first read is also not
populating $a either - my initial tests were with "blah", I hadn't realised
that it hadn't changed to "a" as expected.

So read -t 0 a simply doesn't populate a at all, but returns true.

-- 
You are receiving this mail because:
You are on the CC list for the bug.