linux-kernel - Re: Using best practices for big software change possibilities

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: <20170521102750.ljgvdw2btuks3tqf@ninjato>
Date:   Sun, 21 May 2017 12:27:51 +0200
From:   Wolfram Sang <wsa@...-dreams.de>
To:     SF Markus Elfring <elfring@...rs.sourceforge.net>
Cc:     linux-mm@...ck.org, Dan Streetman <ddstreet@...e.org>,
        Seth Jennings <sjenning@...hat.com>,
        LKML <linux-kernel@...r.kernel.org>,
        kernel-janitors@...r.kernel.org
Subject: Re: Using best practices for big software change possibilities


> How do you think about to resolve them by additional means besides mail exchange?

That can work. E.g. meeting at conferences often solved mail
communication problems.

For now, I still wonder why you were unsure about grouping the changes
into one patch? Maybe there is something to be learned?


Download attachment "signature.asc" of type "application/pgp-signature" (834 bytes)