From: Luc Van Oostenryck <luc.vanoostenryck@gmail.com>
To: Ramsay Jones <ramsay@ramsayjones.plus.com>
Cc: linux-sparse@vger.kernel.org
Subject: Re: [ANNOUNCE] Sparse v0.6.2-rc2
Date: Sat, 20 Jun 2020 16:12:25 +0200 [thread overview]
Message-ID: <20200620141225.q74amobti2us4onq@ltop.local> (raw)
In-Reply-To: <ce3f1a29-e7d1-a18b-dec9-a0e794c6d7ac@ramsayjones.plus.com>
On Sat, Jun 20, 2020 at 01:11:13AM +0100, Ramsay Jones wrote:
>
>
> On 18/06/2020 23:15, Luc Van Oostenryck wrote:
> > Sparse v0.6.2-rc2 is now out.
>
> As expected, no issues found during testing. :-D
>
> Thanks!
Thank you to you!
-- Luc
prev parent reply other threads:[~2020-06-20 14:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-18 22:15 [ANNOUNCE] Sparse v0.6.2-rc2 Luc Van Oostenryck
2020-06-20 0:11 ` Ramsay Jones
2020-06-20 14:12 ` 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=20200620141225.q74amobti2us4onq@ltop.local \
--to=luc.vanoostenryck@gmail.com \
--cc=linux-sparse@vger.kernel.org \
--cc=ramsay@ramsayjones.plus.com \
/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).