From: Christopher Li <sparse@chrisli.org>
To: Linux-Sparse <linux-sparse@vger.kernel.org>
Subject: Sparse 0.4.2-rc1
Date: Mon, 28 Sep 2009 00:33:36 -0700 [thread overview]
Message-ID: <70318cbf0909280033p32c64e2fpbb563ac2b498fa8d@mail.gmail.com> (raw)
I just tagged the sparse git tree with v0.4.2-rc1.
It has been a long while since the last 0.4.1 release.
Al made a big overhaul of the parser to support better
type and attribute parsing. The rest of the changes are
mostly small improvements.
Please give it some test and report back any regression
you find.
Chris
reply other threads:[~2009-09-28 7:33 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=70318cbf0909280033p32c64e2fpbb563ac2b498fa8d@mail.gmail.com \
--to=sparse@chrisli.org \
--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).