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: Thu, 28 Mar 2024 10:11:24 +0100 [thread overview]
Message-ID: <ZgU0PKbECOOBaSZ7@debian> (raw)
In-Reply-To: <CAJgzZoqO_pdy_=+D0AHYhikXMDbTKKn94EttuUeE5EHjxct5vQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1039 bytes --]
Hi Elliott,
On Wed, Mar 27, 2024 at 05:20:18PM -0700, enh wrote:
> > Do you intend to send patches? Otherwise, let me know, and I'll prepare
> > something.
>
> i can do, but it also sounds like enough of a bikeshed that i imagine
> you'd only want to rewrite it again anyway :-)
Actually, I tried to write something, and felt like you'll definitely do
better; I didn't like my text. Please send a patch. (I can do the
bikeshed when applying it, if you don't feel like entertaining it.) :-}
> (i was actually surprised how many references to glibc 2.0 there are
> in various man pages, and even more amused by references to "ancient
> versions of glibc" being defined as "before glibc 2.0", as if 1997
> isn't ancient :-) )
You can move anything like that to HISTORY sections in any page you see
it. In some cases, it might make sense to remove it, but only if it was
a small bug.
Have a lovely day!
Alex
--
<https://www.alejandro-colomar.es/>
Looking for a remote C programming job at the moment.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2024-03-28 9:11 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 ` Alejandro Colomar [this message]
2024-03-30 0:17 ` getpagesize.2 enh
2024-03-30 23:24 ` getpagesize.2 Alejandro Colomar
2024-03-31 21:35 ` getpagesize.2 Alejandro Colomar
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=ZgU0PKbECOOBaSZ7@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