linux-kernel - Re: [v5] Documentation: bootconfig: Update boot configuration documentation

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]

Date:   Thu, 5 Mar 2020 11:19:32 -0800
From:   Randy Dunlap <rdunlap@...radead.org>
To:     Markus Elfring <Markus.Elfring@....de>, linux-doc@...r.kernel.org
Cc:     Masami Hiramatsu <mhiramat@...nel.org>,
        Steven Rostedt <rostedt@...dmis.org>,
        Jonathan Corbet <corbet@....net>, linux-kernel@...r.kernel.org
Subject: Re: [v5] Documentation: bootconfig: Update boot configuration
 documentation

On 3/5/20 11:06 AM, Markus Elfring wrote:
>>>>> Which of the possibly unanswered issues do you find not concrete enough so far?
>>>>
>>>> e.g.:
>>>>>>>  Will the clarification become more constructive for remaining challenges?
>>>
>>> Do you expect that known open issues need to be repeated for each patch revision?
>>
>> Ideally not, but not very much is ideal.
> 
> Did you notice any aspects where I would be still looking for more helpful answers?

Sorry, I haven't been tracking all of the email Q&A/response/replies
all that carefully.

> 
>> IOW, it is sometimes required (if one cares enough; sometimes
>> one just gives up).
> 
> I find this communication detail unfortunate occasionally.

Sure. I do too.

> 
>>> How do you think about the desired tracking of bug reports
>>> also for this software?
> …
>> Masami seems to be responsive.
> 
> The involved contributors show different response delays, don't they?

That's always the case, in any of the Linux subsystems that I have
been involved with.

-- 
~Randy