Linux-man Archive mirror
 help / color / mirror / Atom feed
From: Alejandro Colomar <alx@kernel.org>
To: enh <enh@google.com>
Cc: linux-man <linux-man@vger.kernel.org>,
	"Alejandro Colomar (man-pages)" <alx.manpages@gmail.com>
Subject: Re: getpagesize.2
Date: Sun, 31 Mar 2024 23:35:59 +0200	[thread overview]
Message-ID: <ZgnXQB-vt_lr2lFe@debian> (raw)
In-Reply-To: <ZgifHQoTaDEiga0W@debian>

[-- Attachment #1: Type: text/plain, Size: 1376 bytes --]

Hi Elliott,

On Sun, Mar 31, 2024 at 12:24:12AM +0100, Alejandro Colomar wrote:
> > From e4e24a6a7ef66016edcd735f3cebc7f6583e716a Mon Sep 17 00:00:00 2001
> > From: Elliott Hughes <enh@google.com>
> > Date: Fri, 29 Mar 2024 17:10:26 -0700
> > Subject: [PATCH] getpagesize.2/syscalls.2: modernization.
> > 
> > Remove the HP-UX portability advice, since getpagesize() is a slightly
> > better option than sysconf() for Linux systems.
> > 
> > Explain why this function exists, and why this man page is in the wrong
> > section. (The previous text tried to do both at the same, which was
> > confusing.) Also explain how the vast majority of architectures that
> > don't have a syscall (but do support multiple page sizes) actually work.
> > 
> > Also de-emphasize the glibc 2.0 bug, since most people don't need to
> > worry about compatibility with versions of glibc from 1997.
> > 
> > Finally, change "not on x86" in syscalls.2 to say where there _is_ a
> > syscall.

I've applied it, with my suggestions on top, and pushed it here:
<https://www.alejandro-colomar.es/src/alx/linux/man-pages/man-pages.git/commit/?h=contrib&id=c1e10426dc22ca976ba1107f7ca95a373bb22f83>

It'll stay there for a few days, and then to master.  If you want to
send a Signed-off-by, I'll add it.

Have a lovely night!
Alex

-- 
<https://www.alejandro-colomar.es/>

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

  reply	other threads:[~2024-03-31 21:36 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAJgzZooCY7EV5LZSom08k0wVB2SW3KAk-HL9VMsioxivQB=MeQ@mail.gmail.com>
2024-03-26 23:20 ` getpagesize.2 Alejandro Colomar
2024-03-28  0:20   ` getpagesize.2 enh
2024-03-28  9:11     ` getpagesize.2 Alejandro Colomar
2024-03-30  0:17       ` getpagesize.2 enh
2024-03-30 23:24         ` getpagesize.2 Alejandro Colomar
2024-03-31 21:35           ` Alejandro Colomar [this message]
2024-03-26 22:55 getpagesize.2 enh

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=ZgnXQB-vt_lr2lFe@debian \
    --to=alx@kernel.org \
    --cc=alx.manpages@gmail.com \
    --cc=enh@google.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).