From: Vitaly Chikunov <vt@altlinux.org>
To: Sasha Levin <sashal@kernel.org>
Cc: stable@vger.kernel.org
Subject: Why rolling trees aren't updated last week?
Date: Fri, 1 Apr 2022 05:50:38 +0300 [thread overview]
Message-ID: <20220401025038.d4hpgzpl6jnxkyyw@altlinux.org> (raw)
Hello,
Why linux-rolling-lts and linux-rolling-stable trees aren't updated last
week and stay on the previous lts and stable releases?
Thanks,
next reply other threads:[~2022-04-01 3:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-01 2:50 Vitaly Chikunov [this message]
2022-04-01 5:32 ` Why rolling trees aren't updated last week? 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=20220401025038.d4hpgzpl6jnxkyyw@altlinux.org \
--to=vt@altlinux.org \
--cc=sashal@kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).