linux-kernel - Re: FRV-setup: Clarification for "source code clean-up"?

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 for Android: free password hash cracker in your pocket

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

Date:   Fri, 21 Oct 2016 11:11:54 +0200
From:   SF Markus Elfring <elfring@...rs.sourceforge.net>
To:     Dan Carpenter <dan.carpenter@...cle.com>
Cc:     Jiri Kosina <jikos@...nel.org>,
        Geert Uytterhoeven <geert+renesas@...der.be>,
        LKML <linux-kernel@...r.kernel.org>,
        kernel-janitors@...r.kernel.org
Subject: Re: FRV-setup: Clarification for "source code clean-up"?

> It's all about ratios...  Each clean up patch has chance of introducing
> a bug.

Each update suggestion contains a possibility for mistakes.


> If you only send clean up patches then you only introduce bugs.

I find such a conclusion questionable with the wording "only".


> We really don't want people sending patches if they introduce more bugs
> than they fix.

How do you think about to discuss corresponding software development
statistics in more detail?

Regards,
Markus