<div dir="ltr">i changed to email notification which use now <a href="mailto:digikam-bugs-null@kde.org" style="color:rgb(17,85,204);font-family:arial,sans-serif;font-size:12.8px;font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weight:400;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;background-color:rgb(255,255,255)">digikam-bugs-null@kde.org</a><div><br></div><div>The idea is to CC later the students when a new report is available.</div><div><br></div><div>But i'm not sure if the notification work as expected as this email is prbably used internally from bugzilla.</div><div><br></div><div>Gilles</div></div><div class="gmail_extra"><br><div class="gmail_quote">2018-05-11 12:04 GMT+02:00 Simon Frei <span dir="ltr"><<a href="mailto:freisim93@gmail.com" target="_blank">freisim93@gmail.com</a>></span>:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div text="#000000" bgcolor="#FFFFFF">
No, I think that's too much work for not much gain. It was just an
idea to "misuse" the bugzilla mailing list for these emails too. But
my personal opinion is, that the static check commit emails can be
disabled fully, because they don't have actual information about the
new report. So you need to look at the actual report anyway.<div><div class="h5"><br>
<br>
<div class="m_-8239061041402502462moz-cite-prefix">On 11/05/18 11:38, Gilles Caulier
wrote:<br>
</div>
<blockquote type="cite">
<div dir="ltr">You has right.
<div><br>
</div>
<div>Do you mean to create bugzilla bug reports accordingly with
clang/cppcheck reports ? this will be an hot task todo...</div>
<div><br>
</div>
<div>Gilles</div>
</div>
<div class="gmail_extra"><br>
<div class="gmail_quote">2018-05-11 11:08 GMT+02:00 Simon Frei <span dir="ltr"><<a href="mailto:freisim93@gmail.com" target="_blank">freisim93@gmail.com</a>></span>:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div text="#000000" bgcolor="#FFFFFF"> Hi Gilles,<br>
<br>
Thanks for setting these checks up!<br>
<br>
I'd rather not have automatical emails sent to the
digikam-devel mailing list for the same reason it is now
separate from digikam-bugzilla: Emails in this list should
be actual discussions by humans, not generated mail.
Otherwise the important email may get overlooked. So I
propose to send the updates to digikam-bugzilla or not
send them at all. What do you think?<br>
<br>
Cheers,<br>
Simon
<div>
<div class="m_-8239061041402502462h5"><br>
<br>
<div class="m_-8239061041402502462m_5278238487275645240moz-cite-prefix">On
06/05/18 15:39, Gilles Caulier wrote:<br>
</div>
<blockquote type="cite">
<div dir="ltr">The url has a little bit changed :
<div><br>
</div>
<div><a href="https://www.digikam.org/reports/" target="_blank">https://www.digikam.org/report<wbr>s/</a><br>
</div>
<div><br>
</div>
<div>We have now clang and cppcheck reports posted
to digiKam.org...</div>
<div><br>
</div>
<div>Gilles</div>
</div>
<div class="gmail_extra"><br>
<div class="gmail_quote">2018-05-05 14:19
GMT+02:00 Gilles Caulier <span dir="ltr"><<a href="mailto:caulier.gilles@gmail.com" target="_blank">caulier.gilles@gmail.com</a>></span>:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="ltr">Hi all,
<div><br>
</div>
<div>My Clang static analyzer script is
working well now. It publish in
digiKam.org static area the report
automatically</div>
<div><br>
</div>
<div>url: <a href="https://www.digikam.org/report/" target="_blank">https://www.digikam.org/r<wbr>eport/</a></div>
<div><br>
</div>
<div>The contents is currently and older
one. I will run again the script soon to
update the contents.</div>
<div><br>
</div>
<div>Best</div>
<span class="m_-8239061041402502462m_5278238487275645240HOEnZb"><font color="#888888">
<div><br>
</div>
<div>Gilles</div>
<div><br>
</div>
<div><br>
</div>
</font></span></div>
<div class="m_-8239061041402502462m_5278238487275645240HOEnZb">
<div class="m_-8239061041402502462m_5278238487275645240h5">
<div class="gmail_extra"><br>
<div class="gmail_quote">2018-05-04
17:48 GMT+02:00 Gilles Caulier <span dir="ltr"><<a href="mailto:caulier.gilles@gmail.com" target="_blank">caulier.gilles@gmail.com</a>></span>:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="ltr">Hi all,
<div><br>
</div>
<div>You must know that we parse
norally all source code with
Coverity Scan service and fix
step by step the issues detected
by the static analyzer.</div>
<div><br>
</div>
<div>Since January, git/master
cannot be processed by Coverity.
The build is complete, but the
report is never commited and is
send in somewhere in /dev/nulll
(:=)))...</div>
<div><br>
</div>
<div>Coverity Scan service was
acquired by a new company in
2018, and i suspect a side
effect to commit report to the
remote server. I contacted the
Coverity team, who respond that
investiguation are under
progress, please wait.</div>
<div><br>
</div>
<div>So, i finally try to found a
new solution to parse week by
week all source code to review
by another static analyzer. I
tried Clang one, and reports are
really excellent. I written a
script in project/reports/, but
it's not yet perfect.</div>
<div><br>
</div>
<div>The first report that clang
generate is really interesting.
I shared the files (web pages)
in this archive :</div>
<div><br>
</div>
<div><a href="https://drive.google.com/open?id=1EKr9vAMZFZ8-UDOXXIrzKdlt5G8ClVD1" target="_blank">https://drive.google.com/open?<wbr>id=1EKr9vAMZFZ8-UDOXXIrzKdlt5G<wbr>8ClVD1</a><br>
</div>
<div><br>
</div>
<div>Please take a look and feel
free to apply patches is
necessary.</div>
<div><br>
</div>
<div>I will try to finalize the
script while this week end to be
able to run the analyzer
locally.</div>
<div><br>
</div>
<div>Best</div>
<span class="m_-8239061041402502462m_5278238487275645240m_-1622835431493155084HOEnZb"><font color="#888888">
<div><br>
</div>
<div>Gilles Caulier</div>
</font></span></div>
</blockquote>
</div>
<br>
</div>
</div>
</div>
</blockquote>
</div>
<br>
</div>
</blockquote>
<br>
</div>
</div>
</div>
</blockquote>
</div>
<br>
</div>
</blockquote>
<br>
</div></div></div>
</blockquote></div><br></div>