linux-kernel - Re: [RFC PATCH v1 07/26] docs: reporting-bugs: let users classify their issue

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]

Message-ID: <62356152-a332-692d-ee96-7aba47a666e8@leemhuis.info>
Date:   Sat, 3 Oct 2020 11:42:00 +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 07/26] docs: reporting-bugs: let users classify
 their issue

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 02.10.20 um 18:59 schrieb Randy Dunlap:
> On 10/1/20 1:39 AM, Thorsten Leemhuis wrote:

>> +Linus Torvalds and the leading Linux kernel developers want to see some issues
>> +fixed as soon as possible, hence these 'issues of high priority' get handled
>> +slightly different in the reporting process. Three type of cases qualify:
> 
>             differently
> at least that's what I would say. :)

/me googles

Yeah, seems you are right, thx.

>> +from the old kernel (see below how to archive that). That's because
>                                         achieve
>> +process is sometimes only possible by doing incompatible changes; but to avoid
> eh?  That's because ... ???

Argh, that was a last minute change :-/ Now reads:

That's because incompatible changes sometimes can not be avoided when
implementing big improvements are implemented; but to avoid

>> +regression such changes have to be enabled explicitly during build time
    regressions
>> +configuration.
>> +

Ciao, Thorsten