From: "Cygwin Linux Man Pages Maintainer" <Brian.Inglis@Shaw.ca>
To: "Cygwin Announcements" <cygwin-announce@cygwin.com>
Subject: Updated: man-pages-linux 6.02
Date: Sat, 24 Dec 2022 12:09:54 -0700 [thread overview]
Message-ID: <20221224120954.19176-1-Brian.Inglis@SystematicSW.ab.ca> (raw)
The following package has been upgraded in the Cygwin distribution:
* man-pages-linux 6.02
Documents the Linux kernel system calls and C library interfaces used
by programs, plus system and administrative utilities, devices, file
system, file, and data formats, and related information.
For more information, see the project home page:
https://kernel.org/doc/man-pages/
You may also search and read the pages online:
https://man7.org/linux/man-pages/
although the latest release may not yet be available.
As Cygwin has its own man pages with some conflicts, these man pages
are installed under /usr/share/man/linux/, so by default searching
or viewing these pages requires the option:
$ apropos -m|--systems linux ...
$ man -m|--systems linux ...
Cygwin man pages are under the default system "man", so for convenience
both systems may be specified separated by comma e.g.
$ man -m man,linux ...
The path or option may also be added explicitly to a users MANPATH or
alias e.g.
$ export MANPATH=$MANPATH:/usr/share/man/linux
$ alias apropos='apropos -m man,linux'
$ alias man='man -m man,linux'
Add -a to show both Cygwin and Linux manual pages if present, or swap
the order to prioritize Linux.
Release 6 added some section 2 and 3 pages suffixed by const, head,
or type installed in the base section directory.
For recent changes, please see below, or after installation read
/usr/share/doc/man-pages-linux/Changes:
man-pages-6.02 2022-12-22
Global changes
* Use correct letter case in manual page titles, instead of uppercase.
* Use \" t comments when appropriate (Lintian needs this).
* SYNOPSIS:
- Add _Nullable for functions that receive NULL as a meaningful input.
- Use VLA syntax to clarify the meaning of size parameters, rather
than hiding it in possibly-confusing text. This syntax is not
accepted by any compilers, though.
- Use [[noreturn]] instead of noreturn, which will be deprecated soon.
* Repository documentation:
- Added significant documentation about the repository and the project
in the root of the repository in different files. Starting from the
README, anyone passing by should be able to understand how the
project works and be directed to other documentation files. These
files also document the release process.
- Michael has been busy lately, and he is no longer maintaining the
project. The in-repository documentation mentioned above has been
updated to reflect that.
Changes to individual pages
* copy_file_range.2
Fix wrong kernel version information
* process_madvise.2
Fix capability and ptrace requirements
* madvise.2
Update Transparent Huge Pages file/shmem documentation for Linux 5.4+.
New and rewritten pages
* man3/
static_assert.3
strcpy.3
stpncpy.3
strncat.3
* man3const/
EOF.3const
EXIT_SUCCESS.3const
* man7/
string_copying.7
New and changed links
* man3/
_Static_assert.3 (static_assert(3))
stpcpy.3 (strcpy(3))
strcat.3 (strcpy(3))
strncpy.3 (stpncpy(3))
stpecpy.3 (string_copying(7))
stpecpyx.3 (string_copying(7))
ustpcpy.3 (string_copying(7))
ustr2stp.3 (string_copying(7))
zustr2stp.3 (string_copying(7))
zustr2ustp.3 (string_copying(7))
* man3const/
EXIT_FAILURE.3const (EXIT_SUCCESS(3const))
Newly documented interfaces in existing pages
* ioctl_tty.2
TIOCSERGETLSR
TIOCSER_TEMT
* madvise.2
MADV_COLLAPSE
* syscall.2
loongarch
The manual pages (and other files in the repository) have been improved
beyond what this changelog covers. To learn more about changes applied
to individual pages, use git(1).
reply other threads:[~2022-12-24 19:12 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20221224120954.19176-1-Brian.Inglis@SystematicSW.ab.ca \
--to=brian.inglis@shaw.ca \
--cc=cygwin-announce@cygwin.com \
--cc=cygwin@cygwin.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).