From: Alejandro Colomar <alx.manpages@gmail.com>
To: Brian Inglis <Brian.Inglis@Shaw.ca>,
Linux Man Pages <linux-man@vger.kernel.org>
Subject: Re: [PATCH v3 5/6] man2/chmod.2: add C digit separators to clarify POSIX feature release dates and long numeric digit strings
Date: Wed, 15 Feb 2023 22:10:52 +0100 [thread overview]
Message-ID: <804a2b6d-e1d7-3d23-7768-d0ee4933dd68@gmail.com> (raw)
In-Reply-To: <4c53ab820fbbeb3f3170f8d1d81a14713f256dd9.1676489381.git.Brian.Inglis@Shaw.ca>
[-- Attachment #1.1: Type: text/plain, Size: 3293 bytes --]
Hi Brian,
On 2/15/23 21:17, Brian Inglis wrote:
> ---
> man2/chmod.2 | 30 +++++++++++++++---------------
> 1 file changed, 15 insertions(+), 15 deletions(-)
>
> diff --git a/man2/chmod.2 b/man2/chmod.2
> index 8b5db74ed7e3..674b54368314 100644
> --- a/man2/chmod.2
> +++ b/man2/chmod.2
> @@ -37,7 +37,7 @@ Feature Test Macro Requirements for glibc (see
> .nf
> .BR fchmod ():
> Since glibc 2.24:
> - _POSIX_C_SOURCE >= 199309L
> + _POSIX_C_SOURCE >= 1993\[aq]09L
Please keep all POSIX dates in a single separate patch
(unless there's another reason that I'm not seeing).
Cheers,
Alex
> .\" || (_XOPEN_SOURCE && _XOPEN_SOURCE_EXTENDED)
> glibc 2.19 to glibc 2.23
> _POSIX_C_SOURCE
> @@ -45,7 +45,7 @@ Feature Test Macro Requirements for glibc (see
> _BSD_SOURCE || _POSIX_C_SOURCE
> glibc 2.12 to glibc 2.16:
> _BSD_SOURCE || _XOPEN_SOURCE >= 500
> - || _POSIX_C_SOURCE >= 200809L
> + || _POSIX_C_SOURCE >= 2008\[aq]09L
> glibc 2.11 and earlier:
> _BSD_SOURCE || _XOPEN_SOURCE >= 500
> .\" || (_XOPEN_SOURCE && _XOPEN_SOURCE_EXTENDED)
> @@ -54,7 +54,7 @@ Feature Test Macro Requirements for glibc (see
> .BR fchmodat ():
> .nf
> Since glibc 2.10:
> - _POSIX_C_SOURCE >= 200809L
> + _POSIX_C_SOURCE >= 2008\[aq]09L
> Before glibc 2.10:
> _ATFILE_SOURCE
> .fi
> @@ -82,11 +82,11 @@ The new file mode is specified in
> which is a bit mask created by ORing together zero or
> more of the following:
> .TP 18
> -.BR S_ISUID " (04000)"
> +.BR S_ISUID " (04\[aq]000)"
> set-user-ID (set process effective user ID on
> .BR execve (2))
> .TP
> -.BR S_ISGID " (02000)"
> +.BR S_ISGID " (02\[aq]000)"
> set-group-ID (set process effective group ID on
> .BR execve (2);
> mandatory locking, as described in
> @@ -96,36 +96,36 @@ take a new file's group from parent directory, as described in
> and
> .BR mkdir (2))
> .TP
> -.BR S_ISVTX " (01000)"
> +.BR S_ISVTX " (01\[aq]000)"
> sticky bit (restricted deletion flag, as described in
> .BR unlink (2))
> .TP
> -.BR S_IRUSR " (00400)"
> +.BR S_IRUSR " (00\[aq]400)"
> read by owner
> .TP
> -.BR S_IWUSR " (00200)"
> +.BR S_IWUSR " (00\[aq]200)"
> write by owner
> .TP
> -.BR S_IXUSR " (00100)"
> +.BR S_IXUSR " (00\[aq]100)"
> execute/search by owner ("search" applies for directories,
> and means that entries within the directory can be accessed)
> .TP
> -.BR S_IRGRP " (00040)"
> +.BR S_IRGRP " (00\[aq]040)"
> read by group
> .TP
> -.BR S_IWGRP " (00020)"
> +.BR S_IWGRP " (00\[aq]020)"
> write by group
> .TP
> -.BR S_IXGRP " (00010)"
> +.BR S_IXGRP " (00\[aq]010)"
> execute/search by group
> .TP
> -.BR S_IROTH " (00004)"
> +.BR S_IROTH " (00\[aq]004)"
> read by others
> .TP
> -.BR S_IWOTH " (00002)"
> +.BR S_IWOTH " (00\[aq]002)"
> write by others
> .TP
> -.BR S_IXOTH " (00001)"
> +.BR S_IXOTH " (00\[aq]001)"
> execute/search by others
> .PP
> The effective UID of the calling process must match the owner of the file,
--
<http://www.alejandro-colomar.es/>
GPG key fingerprint: A9348594CE31283A826FBDD8D57633D441E25BB5
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2023-02-15 21:11 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-15 20:15 [PATCH v3 0/6] man2/: use C digit separators, IEC, or ISO multiples to clarify long numeric digit strings Brian Inglis
2023-02-15 20:17 ` Brian Inglis
2023-02-15 20:17 ` [PATCH v3 1/6] man2/: use IEC " Brian Inglis
2023-02-15 21:05 ` Alejandro Colomar
2023-02-16 21:06 ` Stefan Puiu
2023-02-16 23:01 ` Alejandro Colomar
2023-02-16 23:40 ` Brian Inglis
2023-02-16 23:51 ` Alejandro Colomar
2023-02-17 14:05 ` Stefan Puiu
2023-02-19 21:10 ` Alejandro Colomar
2023-02-19 21:12 ` Alejandro Colomar
2023-02-20 14:29 ` Stefan Puiu
2023-02-20 15:35 ` Alex Colomar
2023-02-21 17:00 ` Rob Landley
2023-02-22 1:34 ` Alex Colomar
2023-02-22 22:18 ` Rob Landley
2023-02-24 1:05 ` Alex Colomar
2023-02-16 21:40 ` Jakub Wilk
2023-02-15 20:17 ` [PATCH v3 2/6] man2/keyctl.2: use IEC or ISO multiples or add C digit separators " Brian Inglis
2023-02-15 21:06 ` Alejandro Colomar
2023-02-15 20:17 ` [PATCH v3 3/6] man2/: add C digit separators to clarify POSIX feature release dates Brian Inglis
2023-02-15 21:08 ` Alejandro Colomar
2023-02-16 21:11 ` Stefan Puiu
2023-02-16 23:04 ` Alejandro Colomar
2023-02-17 14:16 ` Stefan Puiu
2023-02-15 20:17 ` [PATCH v3 4/6] man2/select.2: add C digit separators to clarify POSIX feature release dates or use IEC or ISO multiples to clarify long numeric digit strings Brian Inglis
2023-02-15 21:09 ` Alejandro Colomar
2023-02-15 20:17 ` [PATCH v3 5/6] man2/chmod.2: add C digit separators to clarify POSIX feature release dates and " Brian Inglis
2023-02-15 21:10 ` Alejandro Colomar [this message]
2023-02-18 17:42 ` Tom Schwindl
2023-02-18 18:08 ` G. Branden Robinson
2023-02-18 18:31 ` Tom Schwindl
2023-02-18 19:03 ` G. Branden Robinson
2023-02-18 23:32 ` Brian Inglis
2023-02-19 11:50 ` ADA and base prefix for numbers Alejandro Colomar
2023-02-18 18:41 ` [PATCH v3 5/6] man2/chmod.2: add C digit separators to clarify POSIX feature release dates and long numeric digit strings Brian Inglis
2023-02-15 20:17 ` [PATCH v3 6/6] man2/: add C digit separators to clarify " Brian Inglis
2023-02-15 21:14 ` Alejandro Colomar
2023-02-15 22:51 ` [PATCH v3 0/6] man2/: use C digit separators, IEC, or ISO multiples " Brian Inglis
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=804a2b6d-e1d7-3d23-7768-d0ee4933dd68@gmail.com \
--to=alx.manpages@gmail.com \
--cc=Brian.Inglis@Shaw.ca \
--cc=linux-man@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