Why negative to Clang Static Analyzer?
Leslie Zhai
lesliezhai at llvm.org.cn
Sat Dec 2 06:27:59 UTC 2017
Hi KDE developers,
I have fixed 24+ bugs for k3b since 2017.04
https://github.com/KDE/k3b/blob/master/ChangeLog
And my sincere thanks will goto:
* David Faure, he helped me owing to I broke the dependency freeze,
sorry to Albert!
* Thomas Schmitt, he taught me about ISO 9660 and MMC knowledage
patiently and carefully
* Clang Static Analyzer, it hunted the potential bugs
https://bugs.kde.org/show_bug.cgi?id=387298#c11
But why so *IMPATIENT* and *IRRESPONSIBLE* for your commit when clang
static analyzer detected the root cause?! it hurts K3B endusers!
LLVM and KDE developers reviewed the code
https://reviews.llvm.org/p/xiangzhai/ firstly, then it is able to push
to the UPSTREAM repository if LGTM, but why broke the *POLICY*?!
--
Regards,
Leslie Zhai - https://reviews.llvm.org/p/xiangzhai/
More information about the k3b
mailing list