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: Wed, 14 Jun 2017 04:05:40 +0200 [thread overview]
Message-ID: <20170614020538.eve3b6y5di7edtuj@ltop.local> (raw)
In-Reply-To: <CANeU7QkJGdKuiBRw7mFHOh08TTOs=Au6vpgxBkN6LAyV5SvBtg@mail.gmail.com>
On Tue, Jun 13, 2017 at 10:54:45AM -0700, Christopher Li wrote:
> On Mon, Jun 12, 2017 at 9:58 PM, Luc Van Oostenryck
> <luc.vanoostenryck@gmail.com> wrote:
> >
> > 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.
>
> Done. I pushed to master with tag "v0.5.1-rc1".
Thanks.
> > 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.
>
> Sounds good. I think I have review most of them already.
Not the 1st & 3rd here but nothing very special:
- 1st is the following of Al Viro's suggestion for the implicit case
which now also do the same change for the explicit case
- 3rd untangle max_warnings and the fatc that an error has occurred.
> It should be a easy pull. I will create a RC2 after I pull from you.
Good.
-- Luc
prev parent reply other threads:[~2017-06-14 2:05 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
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 [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=20170614020538.eve3b6y5di7edtuj@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