On Tuesday, March 15, 2016 05:45:44 PM Jaroslaw Staniek wrote:
> On 15 March 2016 at 17:33, Tomas Mecir wrote:
> > No change for me, unfortunately, still getting that red box (tried
> > both password and github login).
>
> I see. All I did is asking scan-ad...@coverity.com 2 times or so.
> And w
On 15 March 2016 at 18:10, Frederik Schwarzer wrote:
> I created an account a few weeks ago, asked to join and was able to
> access the KDE group fine the next day. Who is granting the access?
> Maybe contact that person directly.
>
>
Nick Shaforostoff
But I do not mean just the "KDE" scans, t
I created an account a few weeks ago, asked to join and was able to
access the KDE group fine the next day. Who is granting the access?
Maybe contact that person directly.
KDEGames is not there yet, though.
Regards,
Frederik
Am Dienstag, 15. März 2016, 17:45:44 schrieb Jaroslaw Staniek:
> On 1
On 15 March 2016 at 17:33, Tomas Mecir wrote:
> No change for me, unfortunately, still getting that red box (tried
> both password and github login).
>
I see. All I did is asking scan-ad...@coverity.com 2 times or so.
And waiting 2+ weeks. Maybe they're fixing/enabling access one-by-one.
>
No change for me, unfortunately, still getting that red box (tried
both password and github login).
Tomas
2016-03-15 17:28 GMT+01:00 Jaroslaw Staniek :
>
>
> On 28 February 2016 at 16:26, Tomas Mecir wrote:
>>
>> Well, I'd like to, but when I log in and try to access the KDE stuff,
>> I can see
On 28 February 2016 at 16:26, Tomas Mecir wrote:
> Well, I'd like to, but when I log in and try to access the KDE stuff,
> I can see the summary, but accessing the actual defect list gives me a
> red box with this:
>
> It may take a few minutes before you can view your defects, when you
> change
Am Sonntag, 28. Februar 2016, 20:18:22 schrieb Nick Shaforostoff:
> > > Let us know in this thread if code you're interested in isn't
> > > there.>
> > Could we have kdegames there?
>
> ok, i'll include them in the next build (in a week or so)
Thank you.
_
> To be honest, I've tried to use it many times, but I always seem to
> end up diving in warnings in other projects. It's hard to filter for
> projects I have a grasp on.
>
> How do you deal with this?
i just sort by filepath/name (the column is on the right, you need to scroll
horizontally to g
On 28 February 2016 at 20:21, Aleix Pol wrote:
> On Sun, Feb 28, 2016 at 3:59 PM, Jaroslaw Staniek wrote:
> > Hi,
> > Just to remind. If someone has some time to fix bugs, KDE
> > apps/Calligra/Frameworks static analysis is the easiest way to improve
> > Calligra.
> > Code defects are well expla
On Sun, Feb 28, 2016 at 3:59 PM, Jaroslaw Staniek wrote:
> Hi,
> Just to remind. If someone has some time to fix bugs, KDE
> apps/Calligra/Frameworks static analysis is the easiest way to improve
> Calligra.
> Code defects are well explained (like uninitialized variables or
> NULL-related failures
> > Let us know in this thread if code you're interested in isn't there.
> Could we have kdegames there?
ok, i'll include them in the next build (in a week or so)
___
calligra-devel mailing list
calligra-devel@kde.org
https://mail.kde.org/mailman/lis
Am Sonntag, 28. Februar 2016, 15:59:46 schrieb Jaroslaw Staniek:
Hi,
> Let us know in this thread if code you're interested in isn't there.
Could we have kdegames there?
Regards,
Frederik
___
calligra-devel mailing list
calligra-devel@kde.org
https://
On 28 February 2016 at 15:59, Jaroslaw Staniek wrote:
> Hi,
> Just to remind. If someone has some time to fix bugs, KDE
> apps/Calligra/Frameworks static analysis is the easiest way to improve
> Calligra.
> Code defects are well explained (like uninitialized variables or
> NULL-related failures).
On 28 February 2016 at 16:21, Frederik Schwarzer wrote:
> Am Sonntag, 28. Februar 2016, 15:59:46 schrieb Jaroslaw Staniek:
>
> Hi,
>
> > Let us know in this thread if code you're interested in isn't there.
>
> Could we have
>
> kdegames there?
>
> Good idea, CC'd Nick as he updates the builds
On 28 February 2016 at 16:26, Tomas Mecir <
mec...@gmail.com> wrote:
> Well, I'd like to, but when I log in and try to access the KDE stuff,
> I can see the summary, but accessing the actual defect list gives me a
> red box with this:
>
> It may take a few minutes before you can view your defec
Well, I'd like to, but when I log in and try to access the KDE stuff,
I can see the summary, but accessing the actual defect list gives me a
red box with this:
It may take a few minutes before you can view your defects, when you
change your email or password or sign-in with Github for the first
ti
Hi,
Just to remind. If someone has some time to fix bugs, KDE
apps/Calligra/Frameworks static analysis is the easiest way to improve
Calligra.
Code defects are well explained (like uninitialized variables or
NULL-related failures). Much easier than actually reading that bug reports,
analysing them
On Friday June 06 2014 05:46:52 Inge Wallin wrote:
> Of all the category of bugs that the static code analysis can capture, are
> there one or a few that are extra important to fix? If so, then we could
> perhaps put up some wiki page with the analysis result for that type of bug.
Fi
On Thursday, June 05, 2014 22:02:43 Jaroslaw Staniek wrote:
> Dear All,
> Just added a list of tools known as useful in C/C++ static code
> analysis. Some are already used in our development, some need
> volunteers. This is rather very interesting area - let's make Calligra
>
On Jun 05, 2014, at 22:30, Boudewijn Rempt wrote:
>> Prepare yourselves to scan through a lot of output! :)
>
> Did you do that for calligra? Anything we need to fix asap?
No, I said "on my own code", didn't I? :)
I did just verify what I said about the scan-build script on a KDE-related
cmake
On Thu, 5 Jun 2014, "René J.V. Bertin" wrote:
On Jun 05, 2014, at 22:02, Jaroslaw Staniek wrote:
volunteers. This is rather very interesting area - let's make Calligra
more bug-free, and it's relatively cheap!
http://community.kde.org/Calligra/Testing#Static_Code_Analysis
I've already appli
On Jun 05, 2014, at 22:02, Jaroslaw Staniek wrote:
> volunteers. This is rather very interesting area - let's make Calligra
> more bug-free, and it's relatively cheap!
>
> http://community.kde.org/Calligra/Testing#Static_Code_Analysis
I've already applied clang's analyser on code of my own, with
Dear All,
Just added a list of tools known as useful in C/C++ static code
analysis. Some are already used in our development, some need
volunteers. This is rather very interesting area - let's make Calligra
more bug-free, and it's relatively cheap!
http://community.kde.org/Callig
23 matches
Mail list logo
