From: Theodore Tso <tytso@thunk.org>
To: Eric Sandeen <sandeen@redhat.com>
Cc: Andreas Dilger <adilger@clusterfs.com>, linux-ext4@vger.kernel.org
Subject: Re: Coverity testing freely available
Date: Sat, 1 Dec 2007 07:10:39 -0500 [thread overview]
Message-ID: <20071201121039.GD28558@thunk.org> (raw)
In-Reply-To: <47509460.40706@redhat.com>
On Fri, Nov 30, 2007 at 04:53:20PM -0600, Eric Sandeen wrote:
> Andreas Dilger wrote:
> > Hi,
> > I've recently found scan.coverity.com, which allows OSS-licensed projects
> > to be run under Coverity to find defects available in the code. I think
> > that e2fsprogs should be included there, even if some people run e2fsprogs
> > under Coverity separately. This allows the e2fsprogs developers to find
> > and fix the bugs more easily.
> >
>
> I don't see e2fsprogs on the website yet. Anyone care if I go ahead &
> ask that e2fsprogs be included?
I tried sending e-mail to Coverity on July 16th, and never got a
reply. Feel free to give it a try....
- Ted
prev parent reply other threads:[~2007-12-01 17:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-16 8:58 Coverity testing freely available Andreas Dilger
2007-11-30 22:53 ` Eric Sandeen
2007-12-01 12:10 ` Theodore Tso [this message]
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=20071201121039.GD28558@thunk.org \
--to=tytso@thunk.org \
--cc=adilger@clusterfs.com \
--cc=linux-ext4@vger.kernel.org \
--cc=sandeen@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.