From: Alejandro Colomar <alx.manpages@gmail.com>
To: Tom Schwindl <schwindl@posteo.de>, Jakub Wilk <jwilk@jwilk.net>
Cc: linux-man@vger.kernel.org,
"G. Branden Robinson" <g.branden.robinson@gmail.com>
Subject: Re: [PATCH] arc4random.3: New page documenting the arc4random(3) family of functions
Date: Wed, 15 Mar 2023 13:04:29 +0100 [thread overview]
Message-ID: <062a16a8-7057-15d8-eb8a-bfcdb7644ece@gmail.com> (raw)
In-Reply-To: <CR6C48K1388R.2M61G9YHB8VHA@morphine>
[-- Attachment #1.1: Type: text/plain, Size: 1803 bytes --]
Hi Tom & Jakub,
On 3/14/23 19:57, Tom Schwindl wrote:
> On Mon Mar 13, 2023 at 10:30 PM CET, Jakub Wilk wrote:
>> * Alejandro Colomar <alx.manpages@gmail.com>, 2023-01-01 17:26:
>>> +.SH LIBRARY
>>> +Standard C library
>>> +.RI ( libc ", " -lc )
>>
>> That should be \-lc, but...
Ahh, I thought I had fixed that; it seems not. Thanks!
>> To be frank, I'd just remove the whole
>> section. Most people shouldn't use -lc,
While there's no need for most users, it's not wrong to specify it.
I always do it, just for completeness, and treat libc as any other
library.
>> and those who do need it can
>> figure it out on their own.
It's surprising how much trivial knowledge is not taught anywhere
just because it's so trivial, and then it becomes not so trivial
because nobody tells it. I'll keep it just in case. Anyway, I
think being consistent so that all C functions specify a LIBRARY
section is in itself good, since that will probably prompt authors
of pages to use it in their own pages. Also, since I copied this
idea from FreeBSD, it makes sense to follow their decissions unless
we find them harmful.
>>
>
> I don't quite remember what the arguments for the LIBRARY section were,
> but it should be kept for consistency with the other man-pages.
>
>
> off-topic for Alex:
> As we're talking about libc here, what about the libc.7 patch?
> Is there any progress regarding it?
I guess you refer to the patch set by Branden that touched
ldconfig(8), libc(7), and a some more? I guess Branden is busy
with his own stuff (releasing groff-1.23.0). Probably after the
release we'll see some updated patches.
Cheers,
Alex
>
--
<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-03-15 12:06 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-01 16:26 [PATCH] arc4random.3: New page documenting the arc4random(3) family of functions Alejandro Colomar
2023-01-01 16:27 ` Alejandro Colomar
2023-03-17 21:31 ` Jakub Wilk
2023-03-17 21:44 ` Alejandro Colomar
2023-03-17 21:54 ` Alejandro Colomar
2023-01-01 16:39 ` Tom Schwindl
2023-01-01 16:41 ` Alejandro Colomar
2023-01-01 20:48 ` G. Branden Robinson
2023-01-01 20:54 ` Alejandro Colomar
2023-03-13 21:30 ` Jakub Wilk
2023-03-14 18:57 ` Tom Schwindl
2023-03-15 12:04 ` Alejandro Colomar [this message]
2023-03-15 19:37 ` G. Branden Robinson
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=062a16a8-7057-15d8-eb8a-bfcdb7644ece@gmail.com \
--to=alx.manpages@gmail.com \
--cc=g.branden.robinson@gmail.com \
--cc=jwilk@jwilk.net \
--cc=linux-man@vger.kernel.org \
--cc=schwindl@posteo.de \
/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