From: Petr Vorel <pvorel@suse.cz>
To: Jonathan Corbet <corbet@lwn.net>
Cc: linux-doc@vger.kernel.org, Alejandro Colomar <alx@kernel.org>,
man-pages@man7.org
Subject: Re: [PATCH v3 0/3] Documentation: Link man pages to https://man7.org/
Date: Tue, 20 Jan 2026 11:48:14 +0100 [thread overview]
Message-ID: <20260120104814.GA32438@pevik> (raw)
In-Reply-To: <87a4ydo1hf.fsf@trenco.lwn.net>
> Petr Vorel <pvorel@suse.cz> writes:
> > Changes v1->v2:
> > * Remove `...` (italic) from non-existing man pages (Jonathan).
> > * Squash fix for sp_SP to following commit (Jonathan).
> > * Remove :manpage: also from fxyzzy(3) (non-existing man page).
> > * Add CSS for man page.
> > Link to v2:
> > https://lore.kernel.org/linux-doc/20260111233534.183272-1-pvorel@suse.cz/
> > Link to v1:
> > https://lore.kernel.org/linux-doc/20260109183012.114372-1-pvorel@suse.cz/
> > Petr Vorel (3):
> > Documentation: Remove :manpage: from non-existing man pages
> > Documentation: Link man pages to https://man7.org/
> > Documentation: CSS: Improve man page font
> > Documentation/conf.py | 3 +++
> > Documentation/process/adding-syscalls.rst | 16 ++++++++--------
> > Documentation/sphinx-static/custom.css | 8 +++++++-
> > .../it_IT/process/adding-syscalls.rst | 16 ++++++++--------
> > .../sp_SP/process/adding-syscalls.rst | 16 ++++++++--------
> > 5 files changed, 34 insertions(+), 25 deletions(-)
> I have applied this set, thanks.
Thanks!
> Even nicer, of course, would be to have automarkup recognize man-page
> references and add the links automatically so we wouldn't need the
> :manpage: noise. Something for another day, I guess...
Ah, you don't like :manpage: in the rst sources. I try to look into it later.
It looked to me safer than regexp, but hopefully any word following by \([1-8]\)
should be a man page.
Advantage would be that other man pages yet declared would be matched [1],
although some [2] would require to remove code formatting (``...``).
Kind regards,
Petr
[1] https://docs.kernel.org/admin-guide/LSM/Smack.html#file-system-interfaces
[2] https://docs.kernel.org/bpf/prog_cgroup_sysctl.html#context
> Thanks,
> jon
prev parent reply other threads:[~2026-01-20 10:54 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-13 11:36 [PATCH v3 0/3] Documentation: Link man pages to https://man7.org/ Petr Vorel
2026-01-13 11:36 ` [PATCH v3 1/3] Documentation: Remove :manpage: from non-existing man pages Petr Vorel
2026-01-13 11:36 ` [PATCH v3 2/3] Documentation: Link man pages to https://man7.org/ Petr Vorel
2026-01-13 11:36 ` [PATCH v3 3/3] Documentation: CSS: Improve man page font Petr Vorel
2026-01-13 22:45 ` Bagas Sanjaya
2026-01-14 8:36 ` Petr Vorel
2026-01-14 10:33 ` Bagas Sanjaya
2026-01-16 18:29 ` [PATCH v3 0/3] Documentation: Link man pages to https://man7.org/ Jonathan Corbet
2026-01-16 20:37 ` Alejandro Colomar
2026-01-20 10:51 ` Petr Vorel
2026-01-20 10:48 ` Petr Vorel [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=20260120104814.GA32438@pevik \
--to=pvorel@suse.cz \
--cc=alx@kernel.org \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=man-pages@man7.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