From: Carlos O'Donell <carlos@redhat.com>
To: enh <enh@google.com>, Alejandro Colomar <alx@kernel.org>
Cc: linux-man <linux-man@vger.kernel.org>
Subject: Re: drop ia64 from man pages?
Date: Wed, 16 Jul 2025 13:43:36 -0400 [thread overview]
Message-ID: <d27ee305-708f-4733-b8ea-b9e5bac84087@redhat.com> (raw)
In-Reply-To: <CAJgzZoq91VceHKZWetjzr5gOQ=Sx=ReCFfY2erPo7_Dxra9=xA@mail.gmail.com>
On 7/16/25 12:30 PM, enh wrote:
> i didn't look at the other pages, but quite a lot on the clone(2) page
> is actually about what glibc does ... but glibc already removed all
> this stuff. so it should probably not be more than what we have for,
> say, m68k which is just "read your kernel/libc source for more"?
>
> a corollary to "museum hardware should run museum software" might be
> "...and use museum documentation" :-)
Agreed.
There is a balance here between documentation that covers a reasonable
number of use cases, documentation that is easy to maintain, and
documentation that is easy to read (without superfluous information,
either too new or too old).
It has been about 1.5 years since IA64 started being dropped, and I
don't see any reason to keep very specific documentation about it
around except as smaller interesting historical notes.
--
Cheers,
Carlos.
next prev parent reply other threads:[~2025-07-16 17:43 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-16 16:20 drop ia64 from man pages? enh
2025-07-16 16:26 ` Alejandro Colomar
2025-07-16 16:30 ` enh
2025-07-16 17:43 ` Carlos O'Donell [this message]
2025-07-17 10:30 ` Eugene Syromyatnikov
2025-07-17 12:13 ` Carlos O'Donell
2025-07-18 12:18 ` AW: " Walter Harms
2025-07-18 12:37 ` Alejandro Colomar
2025-08-09 8:19 ` Askar Safin
2025-08-09 10:49 ` Alejandro Colomar
2025-08-12 10:37 ` Askar Safin
2025-08-12 10:54 ` Alejandro Colomar
2025-08-13 8:54 ` Eugene Syromyatnikov
2025-07-18 12:43 ` Carlos O'Donell
2025-07-18 13:02 ` Alejandro Colomar
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=d27ee305-708f-4733-b8ea-b9e5bac84087@redhat.com \
--to=carlos@redhat.com \
--cc=alx@kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.