From: Helge Kreutzmann <debian@helgefjell.de>
To: alx.manpages@gmail.com
Cc: mario.blaettermann@gmail.com, linux-man@vger.kernel.org
Subject: Issue in man page syscalls.2
Date: Wed, 1 Nov 2023 14:02:12 +0000 [thread overview]
Message-ID: <ZUJaZL4eHezC6C-F@meinfjell.helgefjelltest.de> (raw)
Without further ado, the following was found:
Issue: And the Linux 6.x series?
"Starting with Linux 2.6.0, the development model changed, and new system "
"calls may appear in each Linux 2.6.x release. In this case, the exact "
"version number where the system call appeared is shown. This convention "
"continues with the Linux 3.x kernel series, which followed on from Linux "
"2.6.39; and the Linux 4.x kernel series, which followed on from Linux 3.19; "
"and the Linux 5.x kernel series, which followed on from Linux 4.20."
next reply other threads:[~2023-11-01 14:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-01 14:02 Helge Kreutzmann [this message]
2023-11-01 16:14 ` Issue in man page syscalls.2 Alejandro Colomar
-- strict thread matches above, loose matches on Subject: below --
2023-11-01 14:02 Helge Kreutzmann
2023-11-01 16:29 ` Alejandro Colomar
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=ZUJaZL4eHezC6C-F@meinfjell.helgefjelltest.de \
--to=debian@helgefjell.de \
--cc=alx.manpages@gmail.com \
--cc=linux-man@vger.kernel.org \
--cc=mario.blaettermann@gmail.com \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).