From: Luc Van Oostenryck <luc.vanoostenryck@gmail.com>
To: Christopher Li <sparse@chrisli.org>
Cc: linux-sparse@vger.kernel.org,
Luc Van Oostenryck <luc.vanoostenryck@gmail.com>
Subject: [GIT PULL] Sparse v0.5.1
Date: Thu, 17 Aug 2017 21:46:39 +0200 [thread overview]
Message-ID: <20170817194639.24300-1-luc.vanoostenryck@gmail.com> (raw)
Chris,
I think we all agree that what we have now is the best we can
have for now and that it's time to make this official.
So, could you, please, pull this patchlet and do everything
needed to make a real release of it?
Many thanks to everyone who contributed to this release, with
a special thank to those who tested the -RCs.
-- Luc Van Oostenryck
The following changes since commit 90859bb4e3f9ad11f76ad42e3dce84043bdc3176:
Bump sparse's version to -rc5 (2017-08-11 18:17:41 +0200)
are available in the git repository at:
git://github.com/lucvoo/sparse.git master
for you to fetch changes up to 720994a58105a531bf53f803b13dd1fedf5c7949:
Sparse v0.5.1 (2017-08-17 21:33:54 +0200)
----------------------------------------------------------------
Luc Van Oostenryck (1):
Sparse v0.5.1
Makefile | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
reply other threads:[~2017-08-17 19:46 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20170817194639.24300-1-luc.vanoostenryck@gmail.com \
--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;
as well as URLs for NNTP newsgroup(s).