From: Pavel Roskin <proski@gnu.org>
To: Dave Jones <davej@redhat.com>
Cc: linux-sparse@vger.kernel.org
Subject: Re: 0.3 ?
Date: Tue, 17 Apr 2007 22:31:14 -0400 [thread overview]
Message-ID: <1176863474.3631.58.camel@dv> (raw)
In-Reply-To: <20070417162947.GA15753@redhat.com>
On Tue, 2007-04-17 at 12:29 -0400, Dave Jones wrote:
> Any plans to do another release sometime soon?
> I'm hitting a segfault with 0.2, that seems to be
> fixed in the current git tree.
Absolutely. It would be very welcome.
I actually developed a habit of never loading any kernel code that
doesn't pass sparse checks on any system I don't want to hang, e.g. if
it's remote, it lacks a reset button or I'm writing an e-mail on it :)
I'm using sparse from git a lot, and whenever I have any issues, they
are in the sources sparse is checking, not in sparse itself. It looks
quite stable to me. It would be great to see sparse 0.3 released soon.
--
Regards,
Pavel Roskin
next prev parent reply other threads:[~2007-04-18 2:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-17 16:29 0.3 ? Dave Jones
2007-04-18 2:31 ` Pavel Roskin [this message]
2007-05-01 18:39 ` Josh Triplett
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=1176863474.3631.58.camel@dv \
--to=proski@gnu.org \
--cc=davej@redhat.com \
--cc=linux-sparse@vger.kernel.org \
/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).