From: Stephen Hemminger <stephen@networkplumber.org>
To: Hoang Le <hoang.h.le@dektech.com.au>
Cc: netdev@vger.kernel.org, tipc-discussion@lists.sourceforge.net
Subject: Re: [iproute2-next v2 1/2] tipc: JSON support for showing nametable
Date: Mon, 11 Jun 2018 08:05:11 -0700 [thread overview]
Message-ID: <20180611080511.0b5a3863@xeon-e3> (raw)
In-Reply-To: <1528683420-15006-1-git-send-email-hoang.h.le@dektech.com.au>
On Mon, 11 Jun 2018 09:16:59 +0700
Hoang Le <hoang.h.le@dektech.com.au> wrote:
> @@ -33,6 +35,8 @@ static void about(struct cmdl *cmdl)
> "\n"
> "Options:\n"
> " -h, --help \t\tPrint help for last given command\n"
> + " -j, --json \t\tJson format printouts\n"
> + " -p, --pretty \t\tpretty print\n"
> "\n"
You should also update manual page: man/man8/tipc-nametable.8
Just cut/paste text from ip or tc pages.
prev parent reply other threads:[~2018-06-11 15:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-11 2:16 [iproute2-next v2 1/2] tipc: JSON support for showing nametable Hoang Le
2018-06-11 2:17 ` [iproute2-next v2 2/2] tipc: JSON support for tipc link printouts Hoang Le
2018-06-11 15:05 ` Stephen Hemminger [this message]
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=20180611080511.0b5a3863@xeon-e3 \
--to=stephen@networkplumber.org \
--cc=hoang.h.le@dektech.com.au \
--cc=netdev@vger.kernel.org \
--cc=tipc-discussion@lists.sourceforge.net \
/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).