public inbox for linux-man@vger.kernel.org
 help / color / mirror / Atom feed
From: "Tom Schwindl" <schwindl@posteo.de>
To: "Jakub Wilk" <jwilk@jwilk.net>,
	"Alejandro Colomar" <alx.manpages@gmail.com>
Cc: <linux-man@vger.kernel.org>
Subject: Re: [PATCH] arc4random.3: New page documenting the arc4random(3) family of functions
Date: Tue, 14 Mar 2023 18:57:49 +0000	[thread overview]
Message-ID: <CR6C48K1388R.2M61G9YHB8VHA@morphine> (raw)
In-Reply-To: <20230313213044.scl37hpwvuyo2dif@jwilk.net>

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... To be frank, I'd just remove the whole 
> section. Most people shouldn't use -lc, and those who do need it can 
> figure it out on their own.
>

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?

-- 
Best Regards,
Tom Schwindl

  reply	other threads:[~2023-03-14 18:58 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 [this message]
2023-03-15 12:04     ` Alejandro Colomar
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=CR6C48K1388R.2M61G9YHB8VHA@morphine \
    --to=schwindl@posteo.de \
    --cc=alx.manpages@gmail.com \
    --cc=jwilk@jwilk.net \
    --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