From: Jonathan E Brassow <jbrassow@redhat.com>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] LVM2 coverity report
Date: Fri, 28 Apr 2006 15:05:37 -0500 [thread overview]
Message-ID: <1a432ac79973c135c73d61ad9cd2080a@redhat.com> (raw)
In-Reply-To: <b2ace7f20604280326t1814bc7ex709b539942b85dc7@mail.gmail.com>
hmmm, tried to sign up... haven't received log in yet...
On Apr 28, 2006, at 5:26 AM, Gildas wrote:
> Hello,
>
> The page http://scan.coverity.com/ shows 33 "Uninspected and Pending"
> bugs for LVM2.
>
> Access seems to be granted to mainteners only and I wondered out of
> pure curiosity if LVM2 developpers were aware of this scan and of its
> results.
>
> Cheers,
> Gildas
> _______________________________________________
> linux-lvm mailing list
> linux-lvm@redhat.com
> https://www.redhat.com/mailman/listinfo/linux-lvm
> read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/
next prev parent reply other threads:[~2006-04-28 20:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-28 10:26 [linux-lvm] LVM2 coverity report Gildas
2006-04-28 20:05 ` Jonathan E Brassow [this message]
2006-05-01 19:12 ` Jonathan E Brassow
2006-05-03 9:52 ` Gildas
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=1a432ac79973c135c73d61ad9cd2080a@redhat.com \
--to=jbrassow@redhat.com \
--cc=linux-lvm@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 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).