From: Alejandro Colomar <alx@kernel.org>
To: Askar Safin <safinaskar@gmail.com>, Michael Kerrisk <mtk@man7.org>
Cc: corbet@lwn.net, linux-doc@vger.kernel.org, man-pages@man7.org,
pvorel@suse.cz
Subject: Re: [PATCH 1/1] Documentation: Link man pages to https://man7.org/
Date: Wed, 14 Jan 2026 21:03:53 +0100 [thread overview]
Message-ID: <aWf1cM9SsMuH-Rxi@devuan> (raw)
In-Reply-To: <20260114195334.3958694-1-safinaskar@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 941 bytes --]
Hi Askar,
On Wed, Jan 14, 2026 at 10:53:34PM +0300, Askar Safin wrote:
> Alejandro Colomar <alx@kernel.org>:
> > FWIW, Michael has been following recent releases of the project quite
> > promptly (faster than distros), so it's reasonable to use it.
Hmmm, he didn't publish 6.16 yet, indeed. I hadn't realized.
> I don't think so. There is still no open_tree(2) on man7.org .
>
> I suggest using https://manpages.debian.org/unstable/ instead.
That would be okay, although Debian is sometimes also a bit laggy.
Arch might be more up-to-date when man7.org isn't.
<https://man.archlinux.org/man/open_tree.2.en>
IIRC, Arch has a good track of being the quickest distro to package new
releases of the Linux man-pages project.
In any case, I think either of man7/Debian unstable/Arch is a relatively
good choice.
Have a lovely night!
Alex
>
> --
> Askar Safin
--
<https://www.alejandro-colomar.es>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2026-01-14 20:03 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
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 [this message]
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=aWf1cM9SsMuH-Rxi@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 \
--cc=safinaskar@gmail.com \
/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.