From: Greg KH <gregkh@linuxfoundation.org>
To: linux-kernel@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>,
torvalds@linux-foundation.org, stable@vger.kernel.org
Cc: lwn@lwn.net, Jiri Slaby <jslaby@suse.cz>
Subject: 5.3.3??? [was Re: Linux 5.3.2]
Date: Tue, 1 Oct 2019 09:07:38 +0200 [thread overview]
Message-ID: <20191001070738.GC2893807@kroah.com> (raw)
In-Reply-To: <20191001070457.GA2893807@kroah.com>
On Tue, Oct 01, 2019 at 09:04:57AM +0200, Greg KH wrote:
> I'm announcing the release of the 5.3.2 kernel.
>
> All users of the 5.3 kernel series must upgrade.
Ok, I messed up this morning and typed "5.3" instead of "5.2" in my
scripts and an "empty" 5.3.3 kernel got released. Well kind of, it got
checked into git, but there wasn't anything to release so things got a
bit confused.
So just consider 5.3.3 a "nothing to see here, ignore the man who forgot
to release kernels _after_ coffee and not before" type of release.
5.3.4 will be the _next_ release after this one, sorry for any
confusion.
ugh,
greg k-h
prev parent reply other threads:[~2019-10-01 7:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-01 7:04 Linux 5.3.2 Greg KH
2019-10-01 7:05 ` Greg KH
2019-10-01 7:07 ` Greg KH [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=20191001070738.GC2893807@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=akpm@linux-foundation.org \
--cc=jslaby@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=lwn@lwn.net \
--cc=stable@vger.kernel.org \
--cc=torvalds@linux-foundation.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