Linux SPARSE checker discussions
 help / color / mirror / Atom feed
From: Luc Van Oostenryck <luc.vanoostenryck@gmail.com>
To: Christopher Li <sparse@chrisli.org>
Cc: Linux-Sparse <linux-sparse@vger.kernel.org>
Subject: Re: Sparse release v0.5.1-rc1
Date: Tue, 13 Jun 2017 06:58:30 +0200	[thread overview]
Message-ID: <20170613045829.p4ilb7xjxg35hzvm@ltop.local> (raw)
In-Reply-To: <CANeU7QnnwD5+XDp-C1-4oxrD8Vn-tMWhoNC8NBv0M36PO9J2fQ@mail.gmail.com>

On Mon, Jun 12, 2017 at 10:05:27AM -0700, Christopher Li wrote:
> Hi,
> 
> 
> I know that sparse has due for a new release for very long time.
> So here it is.

Great!

> I take what is in the spase-next and put them into
> a branch "sparse-0.5.1-rc1".
> 
> https://git.kernel.org/pub/scm/devel/sparse/sparse.git/log/?h=sparse-0.5.1-rc1
> 
> Thanks to Luc Van Oostenryck who contribute a great deal
> of the high quality patches. Sparse should behave much better
> when checking the recent kernel source code.
> 
> Please give the RC1 a good test. Report any problem you found.

I really think that for this it would be better to not have
this rc1 in a separate branch but instead a simple tag in
the master branch, like most projects do.
A lot of people are willing to take the last version of the
master branch but won't bother to checkout another one.
It also conveys the message that this rc1 may be unstable and
too risky for be part of the master branch. It's also not good
for distros and environments which do automatic build, daily
snapshots and such as they won't use another branch.

> Luc, do you have another other bug fix low risk patches you want to
> add in this release? I want to do a quick release then go back to merge
> your other changes.

Nothing really important but I would like to have the following
ones in the release:
- patch "avoid warning on explicit 'bool <- restricted' casts" 
  I would have liked an Acked-by from Al Viro on this one but
  he is quite busy.
- patch "add support for -Wmemcpy-max-count" & friends
  This patch will likely be used for the git tree
- patch "finer control over error vs. warnings"
  which can reveal potential problems which were hidden
- patch "teach cgcc about OSX aka darwin"
- patch "ret-void: warn for implicit type"
- series "testsuite speedup"

I'll send a pull request tomorrow.

-- Luc 

  reply	other threads:[~2017-06-13  4:58 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-12 17:05 Sparse release v0.5.1-rc1 Christopher Li
2017-06-13  4:58 ` Luc Van Oostenryck [this message]
2017-06-13 15:08   ` Ramsay Jones
2017-06-13 16:05     ` Luc Van Oostenryck
2017-06-14  0:00       ` Ramsay Jones
2017-06-14  2:29         ` Luc Van Oostenryck
2017-06-13 17:54   ` Christopher Li
2017-06-14  2:05     ` 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=20170613045829.p4ilb7xjxg35hzvm@ltop.local \
    --to=luc.vanoostenryck@gmail.com \
    --cc=linux-sparse@vger.kernel.org \
    --cc=sparse@chrisli.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