From: Josh Triplett <josh@freedesktop.org>
To: linux-sparse@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Sparse 0.3 version number
Date: Tue, 01 May 2007 19:33:08 -0700 [thread overview]
Message-ID: <4637F864.7090601@freedesktop.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 644 bytes --]
So, the 0.3 release went out...with VERSION=0.2 in the Makefile. Oops.
Fortunately, $(VERSION) currently only affects the version number in the
pkg-config file sparse.pc. If you have written some software that depends on
Sparse, uses pkg-config to check for it with a sufficient version number, and
hoped to depend on 0.3 or newer, my apologies. Fortunately, I suspect few to
no people have done this.
I plan to put out a release shortly with a fix for this, as well as a couple
of additional opportunistic fixes. I also plan to include a "make dist" with
some checks to prevent this from happening again.
- Josh Triplett
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 252 bytes --]
reply other threads:[~2007-05-02 2: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=4637F864.7090601@freedesktop.org \
--to=josh@freedesktop.org \
--cc=linux-kernel@vger.kernel.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).