On 24.03.2020 06:09, Robert Elz wrote:
>     Date:        Tue, 24 Mar 2020 05:40:13 +0100
>     From:        Kamil Rytarowski <n...@gmx.com>
>     Message-ID:  <ea741472-ab1a-9f95-f7ce-72a67608f...@gmx.com>
>   | This patch was sitting in the tree since August 2019.
> In your tree I assume you mean, it certainly hasn't been in mine.

A similar fix was done by shm@ with his public repo in August last year.


That work was not secret as it was presented in at least 2 public and
crowded conference. As far as I recall it was not reported as PR or on a
ML before.

I patched it myself only when I reproduced the problems myself.

> OK, then please revert that change (which cannot be the right fix, regardless
> of what the right one really is) and file a PR, so it can be fixed properly.

OK. I will do it and please fix it in a better way.

> kre
> ps: while looking at this I spotted a (complely unrelated) bug in the same
> file that should be fixed (no, sanitisers will never find this one, but
> human reading easily might) - which I will fix, but I'd prefer to do that
> after this fix is reverted, just so those two commit messages are adjacent.

Thank you in advance!

Attachment: signature.asc
Description: OpenPGP digital signature

Reply via email to