All of lore.kernel.org
 help / color / mirror / Atom feed
From: Josh Triplett <josh@freedesktop.org>
To: Pavel Roskin <proski@gnu.org>
Cc: Dave Jones <davej@redhat.com>, linux-sparse@vger.kernel.org
Subject: Re: 0.3 ?
Date: Tue, 01 May 2007 11:39:41 -0700	[thread overview]
Message-ID: <4637896D.6090700@freedesktop.org> (raw)
In-Reply-To: <1176863474.3631.58.camel@dv>

[-- Attachment #1: Type: text/plain, Size: 1471 bytes --]

Pavel Roskin wrote:
> 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'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.

Your mails made me realize that because Sparse doesn't have a pre-release or
release-candidate process (not yet needed, in my opinion), people don't
necessarily know when I prep for a release and when I just take random
patches.  (Also, most of the most recent patches to Sparse have provided
bugfixes, so it likely still looked like "taking all patches".)  In the
future, I will try to remember to mail the list when I start going into
"process bugfixes and release" mode.

After 0.2, several major chages occurred, such as the impressive new features
from Christopher Li; these patches needed some time to stabilize.  In
addition, I noticed some embarrassing self-warnings and an issue with glibc
2.5.

> 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 :)

Nice to hear. :)

- Josh Triplett


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 252 bytes --]

      reply	other threads:[~2007-05-01 18:39 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
2007-05-01 18:39   ` Josh Triplett [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=4637896D.6090700@freedesktop.org \
    --to=josh@freedesktop.org \
    --cc=davej@redhat.com \
    --cc=linux-sparse@vger.kernel.org \
    --cc=proski@gnu.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 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.