public inbox for linux-man@vger.kernel.org
 help / color / mirror / Atom feed
From: Alejandro Colomar <alx.manpages@gmail.com>
To: Stefan Puiu <stefan.puiu@gmail.com>
Cc: Brian Inglis <Brian.Inglis@shaw.ca>,
	Linux Man Pages <linux-man@vger.kernel.org>
Subject: Re: [PATCH v3 1/6] man2/: use IEC or ISO multiples to clarify long numeric digit strings
Date: Sun, 19 Feb 2023 22:10:36 +0100	[thread overview]
Message-ID: <ed3e2487-2b28-e205-b1aa-c65cb54843ce@gmail.com> (raw)
In-Reply-To: <CACKs7VDaAX=qZh9fhn9wa5L5c4xegF0q+ZDBbzE9KTY9pPN+mQ@mail.gmail.com>


[-- Attachment #1.1: Type: text/plain, Size: 1115 bytes --]

Hi Stefan,

On 2/17/23 15:05, Stefan Puiu wrote:
[...]

>>>> diff --git a/man2/add_key.2 b/man2/add_key.2
>>>> index 56fc6d198d21..215de20baeae 100644
>>>> --- a/man2/add_key.2
>>>> +++ b/man2/add_key.2
>>>> @@ -167,7 +167,7 @@ The size of the string (including the terminating null byte) specified in
>>>>  .I type
>>>>  or
>>>>  .I description
>>>> -exceeded the limit (32 bytes and 4096 bytes respectively).
>>>> +exceeded the limit (32 bytes and 4Ki bytes respectively).
>>>
>>> For what it's worth, I find 4096 much clearer over 4Ki (what is Ki
>>> anyway?). Ditto for 32768 / 32Ki etc. What are we trying to achieve?
>>
>> In this case, we should rather use 4\ KiB, which is standard.
> 
> Maybe it is standard, but why is 4 KiB better / more suitable than 4096?

4 KiB is not that much better than 4096, since 4096 is easy to read.
For higher numbers such as 33554432, it becomes more important to use 32 KiB.
For consistency, using 4 KiB seems reasonable.

Cheers,

Alex

-- 
<http://www.alejandro-colomar.es/>
GPG key fingerprint: A9348594CE31283A826FBDD8D57633D441E25BB5

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2023-02-19 21:10 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 [this message]
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
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=ed3e2487-2b28-e205-b1aa-c65cb54843ce@gmail.com \
    --to=alx.manpages@gmail.com \
    --cc=Brian.Inglis@shaw.ca \
    --cc=linux-man@vger.kernel.org \
    --cc=stefan.puiu@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