cgd@broadcom.com wrote:
 >
> "Why?"  I.e., what's the motivation here?  OK, yeah, it's cute.  But:
> 
> * do other implementations do this?
> 
> * there already _is_ a way to do something like this for people who
>   care (the BLOCKSIZE env var), and there's already -h.

With -h you're not sure its output is GB.
Why do we have -m then? Same in that case.
And... File sizes are growing...

> 
> so, really, the question is, why _should_ we do it, rather than "it's
> fine as is."

Easy scripting... You don't need to set BLOCKSIZE, as with -m

> "Just an idea" is _NOT_ an adequate reason to add a new command line
> switch to a commonly-used and at least somewhat-standard utility.
> 


// M

-- 
Mattias Karlsson
mattias.karlsson@sergei.cc
SysAdm - http://www.sergei.cc/