From: Alejandro Colomar <alx.manpages@gmail.com>
To: "G. Branden Robinson" <g.branden.robinson@gmail.com>
Cc: linux-man@vger.kernel.org
Subject: Re: [PATCH v3 05/13] ldconfig.8: Revise and update for glibc 2.32
Date: Fri, 6 Jan 2023 13:44:45 +0100 [thread overview]
Message-ID: <628cef2b-ce8c-64c1-56bc-c10f2587fa37@gmail.com> (raw)
In-Reply-To: <20230106072020.zpjzc2pk4kjhwotx@illithid>
[-- Attachment #1.1: Type: text/plain, Size: 1748 bytes --]
Hi Branden,
On 1/6/23 08:20, G. Branden Robinson wrote:
> Hi Alex,
>
> At 2023-01-06T02:21:27+0100, Alejandro Colomar wrote:
>> On 1/5/23 23:52, G. Branden Robinson wrote:
>>> * Comment out multiple paragraphs discussing libc4 and libc5 shared
>>> library support. It was removed upstream in July; annotate
>>> commit.
> [...]
>>> +.\" Support for libc4 and libc5 dropped in
>>> +.\" 8ee878592c4a642937152c8308b8faef86bcfc40 (2022-07-14) as "obsolete
>>> +.\" for over twenty years".
>>
>> I prefer removing the code completely. Since removing code is more
>> delicate, and to help whoever may want to investigate history in the
>> future, please do so in a separate commit. I guess it will be better
>> if that commit removing code goes before the general revision of the
>> page.
>
> Okay, will do. I dithered over it because the withdrawn support is such
> a recent change.
While support was removed recently, it's something that was obsolete for
decades, so probably there weren't many users (hopefully none).
> But on the other hand it will take time for man-pages
> 6.02 (or what have you) to percolate out to distributors just as glibc
> 2.32 will.
For users of unstable distributions, we already have 6.02. It took only one
week or so from the day I released it.
alx@debian:~$ apt-cache show manpages-dev | head -n3
Package: manpages-dev
Source: manpages
Version: 6.02-1
Installed-Size: 3698
Maintainer: Dr. Tobias Quathamer <toddy@debian.org>
Architecture: all
Depends: manpages
Suggests: man-browser
Breaks: manpages (<< 6.01-1)
Description-en: Manual pages about using GNU/Linux for development
>
> Regards,
> Branden
--
<http://www.alejandro-colomar.es/>
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2023-01-06 12:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-05 22:52 [PATCH v3 05/13] ldconfig.8: Revise and update for glibc 2.32 G. Branden Robinson
2023-01-06 1:21 ` Alejandro Colomar
2023-01-06 7:20 ` G. Branden Robinson
2023-01-06 12:44 ` Alejandro Colomar [this message]
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=628cef2b-ce8c-64c1-56bc-c10f2587fa37@gmail.com \
--to=alx.manpages@gmail.com \
--cc=g.branden.robinson@gmail.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