Linux kernel -stable discussions
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Acid Bong <acidbong@tilde.cafe>
Cc: stable@vger.kernel.org
Subject: Re: No updates in rolling branches
Date: Mon, 10 Apr 2023 11:02:10 +0200	[thread overview]
Message-ID: <2023041042-irritate-oat-26e0@gregkh> (raw)
In-Reply-To: <D5189C7F-B690-4296-A005-A2C0A1EC85F9@tilde.cafe>

On Mon, Apr 10, 2023 at 11:36:41AM +0300, Acid Bong wrote:
> Hi there, hello,
> 
> I've noticed that the recent (at the moment) releases 6.2.10 and
> 6.1.23 weren't merged into linux-rolling-stable and linux-rolling-lts
> respectively. Is there something wrong with them that they require the
> delay?

Sorry about that, I just forgot to push them out.  They should now be
there (might take a bit for the backend mirrors to sync.)

thanks,

greg k-h

  reply	other threads:[~2023-04-10  9:02 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-10  8:36 No updates in rolling branches Acid Bong
2023-04-10  9:02 ` Greg KH [this message]
2023-04-10  9:26   ` Acid Bong
  -- strict thread matches above, loose matches on Subject: below --
2023-09-12 10:40 Acid Bong
2023-09-12 10:47 ` Greg KH

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=2023041042-irritate-oat-26e0@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=acidbong@tilde.cafe \
    --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