Linux SPARSE checker discussions
 help / color / mirror / Atom feed
From: Luc Van Oostenryck <luc.vanoostenryck@gmail.com>
To: Ramsay Jones <ramsay@ramsayjones.plus.com>
Cc: Christopher Li <sparse@chrisli.org>,
	Linux-Sparse <linux-sparse@vger.kernel.org>,
	Lance Richardson <lrichard@redhat.com>
Subject: Re: Sparse release v0.5.1 RC3
Date: Sat, 1 Jul 2017 22:46:52 +0200	[thread overview]
Message-ID: <20170701204651.gfgarvt6nag7mbur@ltop.local> (raw)
In-Reply-To: <b79fe0eb-06fa-d7fd-67c6-988ed578fbf2@ramsayjones.plus.com>

On Sat, Jul 01, 2017 at 09:31:58PM +0100, Ramsay Jones wrote:
> 
> 
> On 30/06/17 02:30, Christopher Li wrote:
> > I have update the master on sparse git repository to
> > RC3. We actually skip the RC2 on this release.
> > 
> > https://git.kernel.org/pub/scm/devel/sparse/sparse.git/
> > 
> > Compare to RC1, most noticeably fix some "crazy programmer"
> > error on compiling git source code. Thanks Luc for contribute
> > most of the patches from RC1.
> > 
> > Again, please give it a good test. Report back what issue
> > you might find. If there is no big issue, I plan to tag the finial version
> > of v0.5.1 next week.
> 
> Tested on Linux (i686 and x86_64) and cygwin (x86_64).
> 
> Both the sparse testsuite and 'make sparse' on the git tree
> work as expected, without additional failures.
> 
> Thanks! :-D

Thanks again for the testing.

-- Luc 

  reply	other threads:[~2017-07-01 20:46 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-30  1:30 Sparse release v0.5.1 RC3 Christopher Li
2017-07-01 20:31 ` Ramsay Jones
2017-07-01 20:46   ` Luc Van Oostenryck [this message]
2017-07-01 20:37 ` Lance Richardson
2017-07-01 20:45   ` 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=20170701204651.gfgarvt6nag7mbur@ltop.local \
    --to=luc.vanoostenryck@gmail.com \
    --cc=linux-sparse@vger.kernel.org \
    --cc=lrichard@redhat.com \
    --cc=ramsay@ramsayjones.plus.com \
    --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