netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Pavel Šimerda" <pavlix@pavlix.net>
To: netdev@vger.kernel.org
Cc: "Stephen Hemminger" <stephen@networkplumber.org>,
	"Vadim Kochan" <vadim4j@gmail.com>,
	"Daniel Borkmann" <daniel@iogearbox.net>,
	"Phil Sutter" <psutter@redhat.com>,
	"Pavel Šimerda" <psimerda@redhat.com>
Subject: [PATCH iproute2 1/3] ip: fix and extend documentation
Date: Wed, 12 Aug 2015 22:04:06 +0200	[thread overview]
Message-ID: <1439409848-26464-1-git-send-email-pavlix@pavlix.net> (raw)

From: Pavel Šimerda <psimerda@redhat.com>

 * Use unabbreviated `address` and `maddress`
 * Keep only `-n` and `-netns` for network namespace
---
 ip/ip.c       | 4 ++--
 man/man8/ip.8 | 8 ++++----
 2 files changed, 6 insertions(+), 6 deletions(-)

diff --git a/ip/ip.c b/ip/ip.c
index 0cf743f..e75447e 100644
--- a/ip/ip.c
+++ b/ip/ip.c
@@ -48,8 +48,8 @@ static void usage(void)
 	fprintf(stderr,
 "Usage: ip [ OPTIONS ] OBJECT { COMMAND | help }\n"
 "       ip [ -force ] -batch filename\n"
-"where  OBJECT := { link | addr | addrlabel | route | rule | neigh | ntable |\n"
-"                   tunnel | tuntap | maddr | mroute | mrule | monitor | xfrm |\n"
+"where  OBJECT := { link | address | addrlabel | route | rule | neighbor | ntable |\n"
+"                   tunnel | tuntap | maddress | mroute | mrule | monitor | xfrm |\n"
 "                   netns | l2tp | fou | tcp_metrics | token | netconf }\n"
 "       OPTIONS := { -V[ersion] | -s[tatistics] | -d[etails] | -r[esolve] |\n"
 "                    -h[uman-readable] | -iec |\n"
diff --git a/man/man8/ip.8 b/man/man8/ip.8
index 045414d..9da086d 100644
--- a/man/man8/ip.8
+++ b/man/man8/ip.8
@@ -19,8 +19,8 @@ ip \- show / manipulate routing, devices, policy routing and tunnels
 
 .ti -8
 .IR OBJECT " := { "
-.BR link " | " addr " | " addrlabel " | " route " | " rule " | " neigh " | "\
- ntable " | " tunnel " | " tuntap " | " maddr " | "  mroute " | " mrule " | "\
+.BR link " | " address " | " addrlabel " | " route " | " rule " | " neigh " | "\
+ ntable " | " tunnel " | " tuntap " | " maddress " | "  mroute " | " mrule " | "\
  monitor " | " xfrm " | " netns " | "  l2tp " | "  tcp_metrics " }"
 .sp
 
@@ -67,7 +67,7 @@ Output more detailed information.
 
 .TP
 .BR "\-l" , " \-loops " <COUNT>
-Specify maximum number of loops the 'ip addr flush' logic
+Specify maximum number of loops the 'ip address flush' logic
 will attempt before giving up. The default is 10.
 Zero (0) means loop until all addresses are removed.
 
@@ -143,7 +143,7 @@ use the system's name resolver to print DNS names instead of
 host addresses.
 
 .TP
-.BR "\-n" , " \-net" , " \-netns " <NETNS>
+.BR "\-n" , " \-netns " <NETNS>
 switches
 .B ip
 to the specified network namespace
-- 
2.4.1

             reply	other threads:[~2015-08-12 20:08 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-12 20:04 Pavel Šimerda [this message]
2015-08-12 20:04 ` [PATCH iproute2 2/3] ip-link: fix and extend documentation Pavel Šimerda
2015-08-13  6:28   ` vkochan
2015-08-12 20:04 ` [PATCH iproute2 3/3] ip-address: " Pavel Šimerda

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=1439409848-26464-1-git-send-email-pavlix@pavlix.net \
    --to=pavlix@pavlix.net \
    --cc=daniel@iogearbox.net \
    --cc=netdev@vger.kernel.org \
    --cc=psimerda@redhat.com \
    --cc=psutter@redhat.com \
    --cc=stephen@networkplumber.org \
    --cc=vadim4j@gmail.com \
    /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).