tech@mandoc.bsd.lv
 help / color / mirror / Atom feed
From: "Ulrich Spörlein" <uqs@spoerlein.net>
To: tech@mdocml.bsd.lv
Subject: Re: [patch] fix wrong argument for calloc
Date: Sun, 19 May 2013 03:58:56 +0200	[thread overview]
Message-ID: <20130519015855.GI2055@acme.spoerlein.net> (raw)
In-Reply-To: <20130518164545.GC30629@iris.usta.de>

On Sat, 2013-05-18 at 18:45:45 +0200, Ingo Schwarze wrote:
> Hi Ulrich,
> 
> Ulrich Spörlein wrote on Fri, May 17, 2013 at 02:29:10AM +0200:
> 
> > simple patch, please commit.
> 
> Done, both to bsd.lv and openbsd.org.
> 
> > This was found by Coverity Scan CID 978734,
> 
> Hummm...  Please bear with my ignorance...
> How can anybody do anything with the CID?
> Is the CID really useful without a project ID?
> Is there a database somewhere on the net?

Sorry, got to this mail only now. These IDs are unique on
http://scan.coverity.com which is where Open Source projects can sign up
to have Coverity scan their stuff.

The FreeBSD project used to run their own instance of Coverity Prevent
(so with local IDs, not global ones), but I'm trying to get us on the
coverity-run instance, which should scale easier and lessen the
bus-factor on our side.

NetBSD is on there too, maybe OpenBSD should consider doing this as
well.

If you create an account and request access to the FreeBSD project, I
should be able to give that to you. But they currently migrate their
website and some stuff seems broken.

Cheers,
Uli
--
 To unsubscribe send an email to tech+unsubscribe@mdocml.bsd.lv

  reply	other threads:[~2013-05-19  1:59 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-17  0:29 Ulrich Spörlein
2013-05-18 16:45 ` Ingo Schwarze
2013-05-19  1:58   ` Ulrich Spörlein [this message]
2013-05-19 16:11     ` Ingo Schwarze

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=20130519015855.GI2055@acme.spoerlein.net \
    --to=uqs@spoerlein.net \
    --cc=tech@mdocml.bsd.lv \
    /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).