From: Alejandro Colomar <alx@kernel.org>
To: Petr Vorel <pvorel@suse.cz>
Cc: linux-doc@vger.kernel.org, Jonathan Corbet <corbet@lwn.net>,
Michael Kerrisk <mtk@man7.org>,
man-pages@man7.org
Subject: Re: [PATCH 1/1] Documentation: Link man pages to https://man7.org/
Date: Mon, 12 Jan 2026 00:24:00 +0100 [thread overview]
Message-ID: <aWQwVdF3ea1hmgjG@devuan> (raw)
In-Reply-To: <20260111230639.GB170559@pevik>
[-- Attachment #1: Type: text/plain, Size: 968 bytes --]
Hi Petr,
On Mon, Jan 12, 2026 at 12:06:39AM +0100, Petr Vorel wrote:
> > I wonder if this could be implemented in a way that wouldn't need
> > changing any lines of documentation.
>
> Good point. Yes, there is sphinx way to do it as one liner (no need for any
> python scripting):
> https://www.sphinx-doc.org/en/master/usage/configuration.html#confval-manpages_url
>
> But the problem is that it creates links also for non-existing man pages
> (xyzzy(2), xyzzyat(2), fxyzzy(3)) in adding-syscalls.rst. I'll convert them not
> being man pages.
Maybe we could solve that. Do you have a list of undocumented syscalls?
We could quickly add small manual pages for all of them, documenting
only the SYNOPSIS.
The rest of the documentation could come later, but some documentation
would be better than no documentation.
What do you think?
Have a lovely night!
Alex
>
> Kind regards,
> Petr
--
<https://www.alejandro-colomar.es>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2026-01-11 23:24 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-09 18:30 [PATCH 1/1] Documentation: Link man pages to https://man7.org/ Petr Vorel
2026-01-09 20:52 ` Alejandro Colomar
2026-01-11 23:06 ` Petr Vorel
2026-01-11 23:24 ` Alejandro Colomar [this message]
2026-01-11 23:29 ` Petr Vorel
2026-01-11 23:53 ` Alejandro Colomar
2026-01-14 19:53 ` Askar Safin
2026-01-14 20:03 ` Alejandro Colomar
2026-01-15 6:40 ` Petr Vorel
2026-01-15 9:15 ` Michael Kerrisk (man7.org)
2026-01-15 15:10 ` Jonathan Corbet
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=aWQwVdF3ea1hmgjG@devuan \
--to=alx@kernel.org \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=man-pages@man7.org \
--cc=mtk@man7.org \
--cc=pvorel@suse.cz \
/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