From: list at eworm.de (Christian Hesse)
Subject: Coverity + Jenkins
Date: Thu, 8 Oct 2015 22:56:20 +0200 [thread overview]
Message-ID: <20151008225620.0dcdbf1e@leda.localdomain> (raw)
In-Reply-To: <CAHmME9pAsA95N6HRtny8WaioR8Y=6F3MT-iVP2FQM3ZfFBUo4A@mail.gmail.com>
"Jason A. Donenfeld" <Jason at zx2c4.com> on Thu, 2015/10/08 16:33:
> As you probably noticed, I've added cgit to Coverity's scanner. I'm
> still waiting for them to "approve" it as an authentic grass-fed
> no-GMO open source project, but once that happens, we'll have a host
> of bugs to inspect.
We are ready to go... :D
201 defects to be fixed... Though it counts defects from git as well. Is
there a way to exclude pathes? Anybody familiar with coverity?
To avoid duplicate work - who will look at what?
--
main(a){char*c=/* Schoene Gruesse */"B?IJj;MEH"
"CX:;",b;for(a/* Chris get my mail address: */=0;b=c[a++];)
putchar(b-1/(/* gcc -o sig sig.c && ./sig */b/42*2-3)*42);}
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 473 bytes
Desc: OpenPGP digital signature
URL: <http://lists.zx2c4.com/pipermail/cgit/attachments/20151008/09c63dc7/attachment.asc>
next prev parent reply other threads:[~2015-10-08 20:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-08 14:33 Jason
2015-10-08 20:56 ` list [this message]
2015-10-08 21:07 ` mailings
2015-10-08 22:15 ` Jason
2015-10-09 8:54 ` Jason
2015-10-09 8:57 ` mailings
2015-10-09 9:04 ` Jason
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20151008225620.0dcdbf1e@leda.localdomain \
--to=cgit@lists.zx2c4.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).