From: Stephen Hemminger <stephen@networkplumber.org>
To: "積丹尼 Dan Jacobson" <jidanni@jidanni.org>
Cc: netdev@vger.kernel.org
Subject: Re: please add some examples to the ip man page
Date: Tue, 7 Mar 2017 17:25:31 -0800 [thread overview]
Message-ID: <20170307172531.4b15ef47@xeon-e3> (raw)
In-Reply-To: <87bmtc8uk6.fsf@jidanni.org>
On Wed, 08 Mar 2017 08:46:01 +0800
積丹尼 Dan Jacobson <jidanni@jidanni.org> wrote:
> >>>>> "SH" == Stephen Hemminger <stephen@networkplumber.org> writes:
>
> SH> Sure. Submit a patch.
>
> If only I could figure out how to use the command.
$ ip link show
$ ip addr show
$ ip route
next prev parent reply other threads:[~2017-03-08 1:26 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-07 19:10 please add some examples to the ip man page 積丹尼 Dan Jacobson
2017-03-07 19:40 ` Stephen Hemminger
2017-03-08 0:46 ` 積丹尼 Dan Jacobson
2017-03-08 1:25 ` Stephen Hemminger [this message]
2017-03-08 2:20 ` David Ahern
2017-03-08 7:17 ` 積丹尼 Dan Jacobson
2017-03-09 10:56 ` Alexander Alemayhu
2017-03-09 15:17 ` David Ahern
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=20170307172531.4b15ef47@xeon-e3 \
--to=stephen@networkplumber.org \
--cc=jidanni@jidanni.org \
--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).