From: Stephen Hemminger <stephen@networkplumber.org>
To: Christian Hesse <list@eworm.de>
Cc: netdev@vger.kernel.org, Christian Hesse <mail@eworm.de>
Subject: Re: [PATCH 1/1] ip-link: allow human readable output with base of 1024 only for byte counts
Date: Sun, 29 Mar 2015 22:58:35 -0700 [thread overview]
Message-ID: <20150329225835.2cf0f770@uryu.home.lan> (raw)
In-Reply-To: <1427369048-1433-1-git-send-email-list@eworm.de>
On Thu, 26 Mar 2015 12:24:08 +0100
Christian Hesse <list@eworm.de> wrote:
> From: Christian Hesse <mail@eworm.de>
>
> Counting bytes with a base of 1024 is ok. Counting packets, errors, etc
> that way makes no sense.
> So only print byte counts with a base of 1024 if option -iec is given.
>
> Signed-off-by: Christian Hesse <mail@eworm.de>
This changes the output which users expect, especially the packet counts
should follow existing practice. And I doubt anyone would have 1024 errors.
next prev parent reply other threads:[~2015-03-30 5:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-26 11:24 [PATCH 1/1] ip-link: allow human readable output with base of 1024 only for byte counts Christian Hesse
2015-03-30 5:58 ` Stephen Hemminger [this message]
2015-03-30 7:03 ` Christian Hesse
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20150329225835.2cf0f770@uryu.home.lan \
--to=stephen@networkplumber.org \
--cc=list@eworm.de \
--cc=mail@eworm.de \
--cc=netdev@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).