netdev - Re: [patch iproute2 1/2] devlink: write usage help messages to stderr

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20160723094659.06921b95@xeon-e3>
Date:	Sat, 23 Jul 2016 09:46:59 -0700
From:	Stephen Hemminger <stephen@...workplumber.org>
To:	Jiri Pirko <jiri@...nulli.us>
Cc:	netdev@...r.kernel.org, davem@...emloft.net, idosch@...lanox.com,
	eladr@...lanox.com, yotamg@...lanox.com, nogahf@...lanox.com,
	ogerlitz@...lanox.com
Subject: Re: [patch iproute2 1/2] devlink: write usage help messages to
 stderr

On Fri, 22 Jul 2016 18:34:29 +0200
Jiri Pirko <jiri@...nulli.us> wrote:

> From: Jiri Pirko <jiri@...lanox.com>
> 
> In order to not confuse reader, write help messages into stderr.
> 
> Signed-off-by: Jiri Pirko <jiri@...lanox.com>

This does make devlink consistent with other parts of iproute2.
But the most common coding standards, back to Unix, and GNU are
that help messages should go to stdout so that:
  $ ip -h | more
would work as expected.


 http://unix.stackexchange.com/questions/8813/should-the-usage-message-go-to-stderr-or-stdout/8815
 https://www.gnu.org/prep/standards/html_node/_002d_002dhelp.html