From: Luc Van Oostenryck <luc.vanoostenryck@gmail.com>
To: Lance Richardson <lrichard@redhat.com>
Cc: Christopher Li <sparse@chrisli.org>,
Linux-Sparse <linux-sparse@vger.kernel.org>
Subject: Re: Sparse release v0.5.1 RC3
Date: Sat, 1 Jul 2017 22:45:56 +0200 [thread overview]
Message-ID: <20170701204555.vkpl4fsvudsoot6y@ltop.local> (raw)
In-Reply-To: <905534368.29108867.1498941447093.JavaMail.zimbra@redhat.com>
On Sat, Jul 01, 2017 at 04:37:27PM -0400, Lance Richardson wrote:
> > From: "Christopher Li" <sparse@chrisli.org>
> > To: "Linux-Sparse" <linux-sparse@vger.kernel.org>
> > Cc: "Luc Van Oostenryck" <luc.vanoostenryck@gmail.com>, "Lance Richardson" <lrichard@redhat.com>
> > Sent: Thursday, 29 June, 2017 9:30:34 PM
> > Subject: Sparse release v0.5.1 RC3
> >
> > 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.
> >
> > Chris
> >
>
> Hi Chris,
>
> I've tried it against davem's net repository and openvswitch master under
> Fedora 25 x86_64, looks good!
Nice.
Thanks for the testing.
-- Luc
prev parent 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
2017-07-01 20:37 ` Lance Richardson
2017-07-01 20:45 ` 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=20170701204555.vkpl4fsvudsoot6y@ltop.local \
--to=luc.vanoostenryck@gmail.com \
--cc=linux-sparse@vger.kernel.org \
--cc=lrichard@redhat.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