linux-sparse.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ben Dooks <ben.dooks@codethink.co.uk>
To: Luc Van Oostenryck <luc.vanoostenryck@gmail.com>,
	linux-sparse@vger.kernel.org
Cc: "Jeff Layton" <jlayton@redhat.com>,
	"Uwe Kleine-König" <uwe@kleine-koenig.org>
Subject: Re: [ANNOUNCE] Sparse v0.6.4
Date: Mon, 6 Sep 2021 11:04:14 +0100	[thread overview]
Message-ID: <0c4480ce-6c92-7788-772c-581a76c2df51@codethink.co.uk> (raw)
In-Reply-To: <20210906042111.lhoq7egtpmw3jcv6@mail>

On 06/09/2021 05:21, Luc Van Oostenryck wrote:
> Sparse v0.6.4 is now out.
> 
> The source code can be found at its usual repository:
>     git://git.kernel.org/pub/scm/devel/sparse/sparse.git v0.6.4
> 
> The tarballs can be found at:
>     https://www.kernel.org/pub/software/devel/sparse/dist/
> 
> Many thanks to people who have somehow contributed to the 299
> patches of this release:
>     Ramsay Jones, Linus Torvalds, Kyle Russell

This has reminded me I have lost track of the printf formatting
changes. Is it possible to re-sync and work out what still needs
to be done to get this work merged?

-- 
Ben Dooks				http://www.codethink.co.uk/
Senior Engineer				Codethink - Providing Genius

https://www.codethink.co.uk/privacy.html

  reply	other threads:[~2021-09-06 10:32 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-06  4:21 [ANNOUNCE] Sparse v0.6.4 Luc Van Oostenryck
2021-09-06 10:04 ` Ben Dooks [this message]
2021-09-07  6:29   ` Luc Van Oostenryck
2021-09-28 21:05     ` Ben Dooks
2021-09-28 19:56 ` Uwe Kleine-König
2021-09-28 22:43   ` Ramsay Jones
2021-09-29  6:54     ` Uwe Kleine-König
2021-09-29 21:35       ` Ramsay Jones

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=0c4480ce-6c92-7788-772c-581a76c2df51@codethink.co.uk \
    --to=ben.dooks@codethink.co.uk \
    --cc=jlayton@redhat.com \
    --cc=linux-sparse@vger.kernel.org \
    --cc=luc.vanoostenryck@gmail.com \
    --cc=uwe@kleine-koenig.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).