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: <1200338243.31521.10.camel@imap.mvista.com>
Date:	Mon, 14 Jan 2008 11:17:22 -0800
From:	Daniel Walker <dwalker@...sta.com>
To:	Andy Whitcroft <apw@...dowen.org>
Cc:	Stefan Richter <stefanr@...6.in-berlin.de>,
	Bernd Petrovitsch <bernd@...mix.at>,
	linux-kernel@...r.kernel.org, Randy Dunlap <rdunlap@...otime.net>,
	Joel Schopp <jschopp@...tin.ibm.com>,
	Jiri Slaby <jirislaby@...il.com>
Subject: Re: [PATCH] checkpatch.pl: show how to read from stdin


On Mon, 2008-01-14 at 19:12 +0000, Andy Whitcroft wrote:
> So it does, however that of itself differs from the unix norm; as with
> this I cannot run checkpatch and "type" (ie paste) a patch fragment to
> check it.  So I don't think we want the semantics as you have there,
> as its confusing to the experienced user and inconsistent with the
> norm.
> Either we should document the standard '-' usage as has been suggested
> elsewhere or always assume stdin with no parameters.

I'm not sure I understand what you mean .. Can you give an example?

Daniel

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ