[PATCH] doc: mention that ls time ordering is newest first

FYI, in ls.c::usage() (and consequently the man page) I'm adding this non obvious info - otherwise: sort by ctime\n\ + otherwise: sort by ctime, newest first\n\ - -t sort by modification time\n\ + -t

Re: [PATCH] doc: mention that ls time ordering is newest first

Pádraig Brady wrote: > FYI, in ls.c::usage() (and consequently the man page) > I'm adding this non obvious info > > - otherwise: sort by ctime\n\ > + otherwise: sort by ctime, newest first\n\ > > - -t sort by modif

[RFC] closeout redundant diagnostic

I was just testing a framebuffer device here and noticed that there were 2 errors printed by `tr` $ tr '\0' $(($RANDOM % 256)) /dev/full tr: write error: No space left on device tr: write error I was then wondering it there was some other error with the device rather than just filling it. But the

Re: [RFC] closeout redundant diagnostic

On 05/17/2011 05:11 AM, Pádraig Brady wrote: > I was just testing a framebuffer device here and > noticed that there were 2 errors printed by `tr` > > $ tr '\0' $(($RANDOM % 256)) /dev/full > tr: write error: No space left on device > tr: write error > > I was then wondering it there was some oth

Re: [RFC] closeout redundant diagnostic

On 17/05/11 14:48, Eric Blake wrote: > On 05/17/2011 05:11 AM, Pádraig Brady wrote: >> I was just testing a framebuffer device here and >> noticed that there were 2 errors printed by `tr` >> >> $ tr '\0' $(($RANDOM % 256)) /dev/full >> tr: write error: No space left on device >> tr: write error >>