https://bugs.kde.org/show_bug.cgi?id=406645
--- Comment #6 from Christian Gagneraud ---
Thanks a lot for integrating my initial work.
I'll surely report any issue as i start to use this new feature on our code
base.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=406645
Sergio Martins changed:
What|Removed |Added
Resolution|--- |FIXED
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=406645
--- Comment #4 from chg...@gmail.com ---
And there is this script that goes hand in hand with -export-fixes=,
this first run clang-tify in parrallel, then collect, then merge all
replacement files, and finally call clang-apply-replacement if asked to.
https://bugs.kde.org/show_bug.cgi?id=406645
--- Comment #3 from Sergio Martins ---
Thanks! This has been on my TODO list for some time now...
Once this one works I think we should remove the old one from clazy, and only
permit via "clazy-standalone -export-fixes", as the old one has many bugs
https://bugs.kde.org/show_bug.cgi?id=406645
--- Comment #2 from Sergio Martins ---
(Linking https://github.com/KDE/clazy/pull/32 here)
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=406645
Sergio Martins changed:
What|Removed |Added
Assignee|unassigned-b...@kde.org |smart...@kde.org
--
You are receiving this
https://bugs.kde.org/show_bug.cgi?id=406645
--- Comment #1 from chg...@gmail.com ---
See
https://github.com/llvm-mirror/clang-tools-extra/blob/master/clang-tidy/ClangTidy.cpp#L593
--
You are receiving this mail because:
You are watching all bug changes.
