From: Greg KH <gregkh@linuxfoundation.org>
To: Acid Bong <acidbong@tilde.club>
Cc: stable@vger.kernel.org
Subject: Re: No updates in rolling branches
Date: Tue, 12 Sep 2023 12:47:30 +0200 [thread overview]
Message-ID: <2023091227-greedless-handwrite-1c2b@gregkh> (raw)
In-Reply-To: <960C7BCB-CB29-40AE-AA82-CCB470A90DBE@tilde.club>
On Tue, Sep 12, 2023 at 01:40:47PM +0300, Acid Bong wrote:
> Hi there, hello,
>
> I noticed that v6.5.2 already has patches that are not passed to
> v6.4.y, but it's still not merged into `rolling-stable`. Do you not
> merge 6.5.y until 6.4.15 comes to its EOL? Or haven't pushed the
> merge?
We normally move to the "next" stable release for that rolling target
when the number of reports has dropped off and all looks good. That
usually lines up with the EOL time as well. So that means we'll
probably move this later this week.
You are always free to move to the latest release kernel if you want
sooner :)
thanks,
greg k-h
next prev parent reply other threads:[~2023-09-12 10:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-12 10:40 No updates in rolling branches Acid Bong
2023-09-12 10:47 ` Greg KH [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-04-10 8:36 Acid Bong
2023-04-10 9:02 ` Greg KH
2023-04-10 9:26 ` Acid Bong
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=2023091227-greedless-handwrite-1c2b@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=acidbong@tilde.club \
--cc=stable@vger.kernel.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