All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alejandro Colomar <alx@kernel.org>
To: "Štěpán Němec" <stepnem@smrk.net>
Cc: linux-man@vger.kernel.org, "Günther Noack" <gnoack3000@gmail.com>,
	"Mickaël Salaün" <mic@digikod.net>
Subject: Re: [PATCH 3/3] man/man7/landlock.7: wfix
Date: Mon, 20 Jul 2026 00:10:19 +0200	[thread overview]
Message-ID: <al0_v8rno_mZzl0U@devuan> (raw)
In-Reply-To: <20260719211238Z.2327494602-stepnem@smrk.net>

[-- Attachment #1: Type: text/plain, Size: 1689 bytes --]

Hi Štěpán,

On 2026-07-19T23:12:38+0200, Štěpán Němec wrote:
> On Sat, 18 Jul 2026 14:17:57 +0200
> Alejandro Colomar wrote:
> 
> > On 2026-07-13T13:48:55+0200, Štěpán Němec wrote:
> >> FWIW I see little point in this kind of duplication, given
> >> that the kernel docs are as readily available to anyone
> >> interested as the man pages are;
> >
> > Not so much; the manual pages are available for anyone on a terminal
> > without internet connection.  The kernel docs are only available if you
> > have the kernel sources or internet.
> 
> No, I really don't see a difference here: I don't know a
> Linux distro that doesn't provide the kernel docs as a
> package.  (You seem to be using Debian and/or its
> derivatives, so that would be the linux-doc package.)

Hmmm, thanks!  I didn't know about it.  Still, I find local html docs to
be less comfortable for users than manual pages, but it's good to know
that it exists.


Have a lovely night!
Alex

> > So, the manual pages are necessary.  What I wonder is if the kernel
> > documentation is necessary.  I think they could drop it (the duplicated
> > part of it), and refer to the manual page.  However, I trust they know
> > what's best for them.
> 
> In principle, if the docs are maintained by kernel
> developers, the other way round, i.e., preferring the kernel
> docs, makes more sense to me: being in the same source tree,
> their maintenance is less likely to be forgotten or
> neglected (there might also be other factors, such as reST
> likely being less taxing to work with than roff for most
> people).
> 
> -- 
> Štěpán

-- 
<https://www.alejandro-colomar.es>

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2026-07-19 22:10 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-09 15:34 [PATCH 1/3] man/: tfix Štěpán Němec
2026-07-09 15:34 ` [PATCH 2/3] man/man7/pipe.7: Note kernel commit of the soft limit triggered cap increase Štěpán Němec
2026-07-10 16:46   ` Alejandro Colomar
2026-07-09 15:34 ` [PATCH 3/3] man/man7/landlock.7: wfix Štěpán Němec
2026-07-10 16:48   ` Alejandro Colomar
2026-07-13 11:48     ` Štěpán Němec
2026-07-18 12:17       ` Alejandro Colomar
2026-07-19 21:12         ` Štěpán Němec
2026-07-19 22:10           ` Alejandro Colomar [this message]
2026-07-10 16:44 ` [PATCH 1/3] man/: tfix Alejandro Colomar
2026-07-13 12:11   ` [PATCH] man/man2/memfd_secret.2: tfix Štěpán Němec
2026-07-18 12:08     ` 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=al0_v8rno_mZzl0U@devuan \
    --to=alx@kernel.org \
    --cc=gnoack3000@gmail.com \
    --cc=linux-man@vger.kernel.org \
    --cc=mic@digikod.net \
    --cc=stepnem@smrk.net \
    /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.