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: Tue, 31 Aug 2021 14:58:48 +0200 [thread overview]
Message-ID: <20210831125848.mqkudmaz4innkst4@mail> (raw)
In-Reply-To: <72eec6322944bc2fc91e053565fb27ee4aaa203f.camel@kernel.org>
> Hi Luc,
>
> Just checking back in. Were you still planning to do an -rc for 0.6.4?
>
> Thanks,
Hi,
Sorry, I've had a few unplanned things to handle here.
I'll do a -rc1 this evening, when I'm back home and,
if everything is fine, as I hope it will, the release somewhere
between Friday & Saturday.
-- Luc
next prev parent reply other threads:[~2021-08-31 12:58 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
2021-07-27 12:48 ` Jeff Layton
2021-08-31 12:51 ` Jeff Layton
2021-08-31 12:58 ` Luc Van Oostenryck [this message]
-- 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=20210831125848.mqkudmaz4innkst4@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 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 read-only IMAP folder(s) and NNTP newsgroup(s).