From: Christopher Li <sparse@chrisli.org>
To: Jeff Layton <jlayton@poochiereds.net>
Cc: linux-sparse@vger.kernel.org, Josh Triplett <josh@kernel.org>
Subject: Re: new sparse release?
Date: Fri, 25 Sep 2009 10:12:32 -0700 [thread overview]
Message-ID: <70318cbf0909251012q6e21a7b6g96c68351c19c772a@mail.gmail.com> (raw)
In-Reply-To: <20090925083109.18353a08@tlielax.poochiereds.net>
On Fri, Sep 25, 2009 at 5:31 AM, Jeff Layton <jlayton@poochiereds.net> wrote:
> The sparse package in Fedora is based on the latest release of sparse
> (0.4.1). That seems to be really old (from 2007) and is lacking
> important patches (like the one to ignore the __cold__ attribute).
>
> Would it be possible to cut a newer release sometime in the near future
> so that distros can pick up a new official version?
>
Sure, I mean to do that. Currently the sparse wiki is up. I have been
syncing bits from chrisl branch from time to time.
I just need to:
- Get a PGP key.
- Sign the new release tag.
- Run magic git command to generate stat of changes.
- Add change log.
- make dist.
- Upload the tar package.
- Announce the release to mailing list.
I will cut 0.4.2.0-rc1 one over the week end.
Thanks
Chris
next prev parent reply other threads:[~2009-09-25 17:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-25 12:31 new sparse release? Jeff Layton
2009-09-25 17:12 ` Christopher Li [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-07-26 11:20 Jeff Layton
2021-07-26 15:50 ` Luc Van Oostenryck
2021-07-27 12:48 ` Jeff Layton
2021-08-31 12:51 ` Jeff Layton
2021-08-31 12:58 ` Luc Van Oostenryck
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=70318cbf0909251012q6e21a7b6g96c68351c19c772a@mail.gmail.com \
--to=sparse@chrisli.org \
--cc=jlayton@poochiereds.net \
--cc=josh@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).