linux-kernel - Re: [RFC PATCH v1 24/26] docs: reporting-bugs: explain why users might get neither reply nor fix

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: <1d03f885-aa9a-b531-de95-57b8c6e958ab@leemhuis.info>
Date:   Sun, 4 Oct 2020 08:35:54 +0200
From:   Thorsten Leemhuis <linux@...mhuis.info>
To:     Randy Dunlap <rdunlap@...radead.org>,
        Jonathan Corbet <corbet@....net>
Cc:     linux-doc@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [RFC PATCH v1 24/26] docs: reporting-bugs: explain why users
 might get neither reply nor fix

Many thx for you comments. Consider all the obvious spelling and

grammatical mistakes you pointed out fixed, I won't mention all of them

in this reply to keep things easier to follow.



Am 04.10.20 um 06:03 schrieb Randy Dunlap:
> On 10/1/20 1:50 AM, Thorsten Leemhuis wrote:

>> +selling new hardware; quite a few of them hence are not investing much time and
>> +energy in maintaining a Linux kernel driver for something they sold years ago.
>> +Enterprise Linux distributors often care for a longer time period, but in new
>> +version often leave support for old and rare hardware aside to limit the scope.
>> +Often spare time contributors take over once a company leaves some orphan some
>                                                                   drop last: some
>> +code, 

/me looks closer

Changed to (that's what it was supposed to be):

Often spare time contributors take over once a company orphans some
code, […]

Ciao, Thorsten