From: Luc Van Oostenryck <luc.vanoostenryck@gmail.com>
To: Jeff Layton <jlayton@kernel.org>
Cc: linux-sparse@vger.kernel.org,
Luc Van Oostenryck <luc.vanoostenryck.ml@gmail.com>
Subject: Re: new sparse release?
Date: Mon, 26 Jul 2021 17:50:45 +0200 [thread overview]
Message-ID: <20210726155045.fo6nh4lryln5sgxl@mail> (raw)
In-Reply-To: <c7963e9e4c7d5b91fc8bee9c9ae9a9c893664e0b.camel@kernel.org>
On Mon, Jul 26, 2021 at 07:20:28AM -0400, Jeff Layton wrote:
> It's been quite a while since we've had a new sparse release and there
> are some fixes that I'd like to see in the fedora package. I could just
> cut a release from a current git snapshot, but I don't want to do that
> if there are any plans to do a release soon.
>
> Any idea when the next sparse release will be?
I've been quite a bit side-tracked lately and as such I had nothing
really planned. But yes, it's been a while with enough changes already.
I've a few minor fixes I would like to add and a bigger series (but
one 'm not really happy with). I'll see what I can do n the next days
but the idea would be to do a -rc next WE and the full release a few
days later (so around Aug 5) if nothing serious come up.
Would this be OK for you?
-- Luc
next prev parent reply other threads:[~2021-07-26 15:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-26 11:20 new sparse release? Jeff Layton
2021-07-26 15:50 ` Luc Van Oostenryck [this message]
2021-07-27 12:48 ` Jeff Layton
2021-08-31 12:51 ` Jeff Layton
2021-08-31 12:58 ` Luc Van Oostenryck
-- strict thread matches above, loose matches on Subject: below --
2009-09-25 12:31 Jeff Layton
2009-09-25 17:12 ` Christopher Li
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=20210726155045.fo6nh4lryln5sgxl@mail \
--to=luc.vanoostenryck@gmail.com \
--cc=jlayton@kernel.org \
--cc=linux-sparse@vger.kernel.org \
--cc=luc.vanoostenryck.ml@gmail.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 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.