From: Jason at zx2c4.com (Jason A. Donenfeld)
Subject: Coverity + Jenkins
Date: Fri, 9 Oct 2015 00:15:38 +0200 [thread overview]
Message-ID: <CAHmME9qKuQ35UYzMqkX-52rDMwYYUPO-b2g4Zg2=_zxuwUKp8Q@mail.gmail.com> (raw)
In-Reply-To: <5616DB2E.6070803@hupie.com>
The majority of them are from git. There's a way to organize the code
into modules so that we don't have to look at the git bugs though.
I'll investigate this tomorrow, unless someone beats me to it.
next prev parent reply other threads:[~2015-10-08 22:15 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
2015-10-08 21:07 ` mailings
2015-10-08 22:15 ` Jason [this message]
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='CAHmME9qKuQ35UYzMqkX-52rDMwYYUPO-b2g4Zg2=_zxuwUKp8Q@mail.gmail.com' \
--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).