From: Alejandro Colomar <alx@kernel.org>
To: "Pádraig Brady" <P@draigbrady.com>
Cc: coreutils@gnu.org, linux-man@vger.kernel.org
Subject: Re: Hand-written manual pages for GNU coreutils
Date: Sat, 18 Jul 2026 19:46:57 +0200 [thread overview]
Message-ID: <alu6W-eLOScmLJ3p@devuan> (raw)
In-Reply-To: <9d03b838-eec1-499b-a55f-047cc7e2ef92@draigBrady.com>
[-- Attachment #1: Type: text/plain, Size: 2407 bytes --]
Hi Pádraig,
On 2026-07-18T18:02:43+0100, Pádraig Brady wrote:
> On 18/07/2026 16:13, Alejandro Colomar wrote:
> > Hi!
> >
> > I've started working on improving the quality of the manual pages for
> > coreutils, as I promised some time ago I'd do. The work is --for the
> > moment-- in the 'coreutils' branch of the Linux man-pages repo. Once
> > I finish, they won't be auto-generated from --help anymore.
> >
> > <https://git.kernel.org/pub/scm/docs/man-pages/man-pages.git/log/?h=coreutils>
> >
> > We'll talk about incorporation to the coreutils.git repo later.
>
> For reference, it was previously discussed at:https://lists.gnu.org/archive/html/coreutils/2025-09/msg00151.html
> For clarifications on any details, please see the full documentation
> for any command at the link at the bottom of the coreutils man page.
>
> E.g. `man vdir` references https://www.gnu.org/software/coreutils/vdir
The link doesn't work for me at the moment, but I've found the
differences between ls/dir/vdir here:
<https://unix.stackexchange.com/a/344222/341413>.
>
> Also note that since v9.10 each coreutils man page has deep links
> from each option in the man page to the corresponding description
> in the full documentation. That is something that could be maintained
> in any forked man pages.
Yup, I noticed that a moment ago. I'll keep those links. :)
I've done the initial import with this:
$ dpkg -l coreutils \
| tail -n1;
ii coreutils 9.10-1devuan1 amd64 GNU core utilities
$ apt-file show coreutils \
| grep man1/ \
| cut -f2 -d' ' \
| xargs -I{} find {} -type f
| xargs cp -t man1/;
$ apt-file show coreutils \
| grep man8/ \
| cut -f2 -d' ' \
| xargs -I{} find {} -type f
| xargs cp -t man8/;
$ find man -type f \
| grep '\.gz$' \
| xargs gunzip;
It's 9.10, so I guess it has everything. If there's any page that is
not available in Devuan, or there's any change in git that you haven't
released yet and want to include, just let me know.
Have a lovely day!
Alex
> cheers,
> Padraig
--
<https://www.alejandro-colomar.es>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2026-07-18 17:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-18 15:13 Hand-written manual pages for GNU coreutils Alejandro Colomar
2026-07-18 15:42 ` ls/dir/vdir(1) Alejandro Colomar
2026-07-18 18:15 ` ls/dir/vdir(1) Ivan Sokolov
2026-07-18 17:02 ` Hand-written manual pages for GNU coreutils Pádraig Brady
2026-07-18 17:46 ` 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=alu6W-eLOScmLJ3p@devuan \
--to=alx@kernel.org \
--cc=P@draigbrady.com \
--cc=coreutils@gnu.org \
--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