From: Turritopsis Dohrnii Teo En Ming <teo.en.ming@protonmail.com>
To: "linux-newbie@vger.kernel.org" <linux-newbie@vger.kernel.org>
Cc: "ceo@teo-en-ming-corp.com" <ceo@teo-en-ming-corp.com>
Subject: [Linux Newbie] I can't catch up with Linux Kernel releases
Date: Thu, 08 Feb 2024 12:55:01 +0000 [thread overview]
Message-ID: <H0q1TqL1vn5O2AE6wnfjosvchWG48BrZEmGmE2nurw02T6IhxxLvUPyrYcLx4s2-SW0s8OW9NssUlnheB2NJ59Zhqvg8mI64e5meafWDnyI=@protonmail.com> (raw)
Subject: [Linux Newbie] I can't catch up with Linux Kernel releases
Good day from Singapore,
Not too long ago, I installed Arch Linux with Kernel 6.6.7 on my refurbished Aftershock gaming laptop. The latest release is now 6.7.4.
Looks like I won't be able to keep up with the pace of Linux Kernel releases unless I stick to Arch Linux, a rolling release Linux distribution.
Regards,
Mr. Turritopsis Dohrnii Teo En Ming
Targeted Individual in Singapore
Blogs:
https://tdtemcerts.blogspot.com
https://tdtemcerts.wordpress.com
GIMP also stands for Government-Induced Medical Problems.
next reply other threads:[~2024-02-08 12:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-08 12:55 Turritopsis Dohrnii Teo En Ming [this message]
2024-03-18 0:50 ` [Linux Newbie] I can't catch up with Linux Kernel releases Jonathan Martin
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='H0q1TqL1vn5O2AE6wnfjosvchWG48BrZEmGmE2nurw02T6IhxxLvUPyrYcLx4s2-SW0s8OW9NssUlnheB2NJ59Zhqvg8mI64e5meafWDnyI=@protonmail.com' \
--to=teo.en.ming@protonmail.com \
--cc=ceo@teo-en-ming-corp.com \
--cc=linux-newbie@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).