From: Jiri Benc <jbenc@redhat.com>
To: Hangbin Liu <liuhangbin@gmail.com>
Cc: network dev <netdev@vger.kernel.org>
Subject: Re: [patch iproute2] ipaddress: add a black line for each device to make the output more readable
Date: Mon, 11 Nov 2013 17:31:00 +0100 [thread overview]
Message-ID: <20131111173100.108e9026@griffin> (raw)
In-Reply-To: <1384182210-8901-1-git-send-email-liuhangbin@gmail.com>
On Mon, 11 Nov 2013 23:03:30 +0800, Hangbin Liu wrote:
> When we have multi links, the output huddled together and make it hard to read.
> Let's use the old ifconfig output style.
No. You can't break others' scripts like that.
bash$ function ip { /sbin/ip "$@" | sed '2,$s/^[0-9]*:/\n&/' ; }
^^^ Here, fixed that for you.
Jiri
--
Jiri Benc
next prev parent reply other threads:[~2013-11-11 16:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-11 15:03 [patch iproute2] ipaddress: add a black line for each device to make the output more readable Hangbin Liu
2013-11-11 15:08 ` Hangbin Liu
2013-11-11 16:31 ` Jiri Benc [this message]
2013-11-12 2:09 ` Hangbin Liu
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=20131111173100.108e9026@griffin \
--to=jbenc@redhat.com \
--cc=liuhangbin@gmail.com \
--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).