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: <trinity-423abc00-b03e-4813-a090-da059bb5ee4e-1465992097699@3capp-webde-bap45>
Date:	Wed, 15 Jun 2016 14:01:37 +0200
From:	"SF Markus Elfring" <elfring@...rs.sourceforge.net>
To:	"Luis R. Rodriguez" <mcgrof@...nel.org>
Cc:	Gilles.Muller@...6.fr, nicolas.palix@...g.fr, mmarek@...e.com,
	linux-kernel@...r.kernel.org, cocci@...teme.lip6.fr
Subject: Aw: [Cocci] [PATCH 2/4] scripts: add reqs python library

> +class Req:

Will a longer identifier like "requirement" be more useful than the suggested abbreviation?


> +    "To be used for verifying binay package dependencies on Python code"

Would you like to fix a typo here?

... binary ...


> +    def req_old_program(self, program, version_req):

Does such a name selection need also further considerations?

Regards,
Markus

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ