All of lore.kernel.org
 help / color / mirror / Atom feed
From: Lance Richardson <lrichard@redhat.com>
To: Christopher Li <sparse@chrisli.org>
Cc: Linux-Sparse <linux-sparse@vger.kernel.org>,
	Luc Van Oostenryck <luc.vanoostenryck@gmail.com>
Subject: Re: Sparse release v0.5.1 RC3
Date: Sat, 1 Jul 2017 16:37:27 -0400 (EDT)	[thread overview]
Message-ID: <905534368.29108867.1498941447093.JavaMail.zimbra@redhat.com> (raw)
In-Reply-To: <CANeU7Q=q8PVxavt1CegVebT9aSnQ2ugXrE4PStf7ey08Kg+NpA@mail.gmail.com>

> 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!

Thanks,

   Lance

  parent reply	other threads:[~2017-07-01 20:37 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 [this message]
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=905534368.29108867.1498941447093.JavaMail.zimbra@redhat.com \
    --to=lrichard@redhat.com \
    --cc=linux-sparse@vger.kernel.org \
    --cc=luc.vanoostenryck@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.