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  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:   Fri, 12 Jun 2020 20:43:41 +0200
From:   Markus Elfring <>
To:     Matthew Wilcox <>,
        Kaitao Cheng <>,
        Alexey Dobriyan <>,
        Colin Ian King <>,
        Muchun Song <>
Subject: Re: [v2] proc/fd: Remove unnecessary variable initialisations in

>> The presented suggestions trigger different views by involved contributors.
> Most of the views I've heard are "Markus, go away".
> Do you not hear these views?

I notice also this kind of feedback.
The clarification is still evolving for these concerns and communication difficulties.

I suggest to take another look at published software development activities.

>> In which directions can the desired clarification evolve?
> You could try communicating in a way that the rest of us do.

I got also used to some communication styles.
I am curious to find the differences out which hinder to achieve a better
common understanding.

> For example, instead of saying something weird about "collateral evolution"
> you could say "I think there's a similar bug here".

* Why do you repeat this topic here?

* Do try to distract from implementation details which were pointed out
  by two developers for this patch?

>> How do you think about further function design alternatives?
> Could you repeat that in German?  I don't know what you mean.

I imagine that you could know affected software aspects better.


Powered by blists - more mailing lists