From: "Tom Schwindl" <schwindl@posteo.de>
To: "Alejandro Colomar" <alx.manpages@gmail.com>,
"Brian Inglis" <Brian.Inglis@Shaw.ca>
Cc: "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: Sat, 18 Feb 2023 17:42:05 +0000 [thread overview]
Message-ID: <CQLVH6DLAYFQ.T4VQOGPPW8CP@morphine> (raw)
In-Reply-To: <804a2b6d-e1d7-3d23-7768-d0ee4933dd68@gmail.com>
Hi Alex,
On Wed Feb 15, 2023 at 10:10 PM CET, Alejandro Colomar wrote:
> 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).
As long as I'm not completely lost, those values are often passed on the command
line via `-D`. Wouldn't a random \[aq] interfere with shell quoting and result in
hard to find bugs and unexpected bahavior? So is it really a good idea to present
those values in such a way in the manpage? Or am I simply underestimating the
intelligence of the readers? :-)
--
Best Regards,
Tom Schwindl
>
> Cheers,
>
> Alex
next prev parent reply other threads:[~2023-02-18 17:43 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
2023-02-18 17:42 ` Tom Schwindl [this message]
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=CQLVH6DLAYFQ.T4VQOGPPW8CP@morphine \
--to=schwindl@posteo.de \
--cc=Brian.Inglis@Shaw.ca \
--cc=alx.manpages@gmail.com \
--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