From: Sven Hoexter <sven@stormbind.net>
To: "Michael Kerrisk (man-pages)" <mtk.manpages@gmail.com>
Cc: linux-man <linux-man@vger.kernel.org>
Subject: Re: [patch] update kernel documentation references in cgroups(7) and cpuset(7)
Date: Mon, 29 Jun 2020 14:07:59 +0200 [thread overview]
Message-ID: <20200629120759.GA14586@stormbind.net> (raw)
In-Reply-To: <CAKgNAkjJDC3ejYqh8sqg7Ka_yh+=TAdvi-=suHEihjqsbvGnpA@mail.gmail.com>
On Mon, Jun 29, 2020 at 01:40:50PM +0200, Michael Kerrisk (man-pages) wrote:
> On Fri, 19 Jun 2020 at 18:35, Sven Hoexter <sven@stormbind.net> wrote:
Hi,
> > cgroups-v1/v2 documentation got moved to the "admin-guide" subfolder
> > and converted from .txt files to .rst
>
> Thanks for your patch and for the ping, and sorry I did not respond
> earlier. I had not forgotten this patch, but I was still working out
> what to do with it.
>
> The general philosophy in man-pages is to maintain historical
> information, since the man-pages that are installed on a system may
> not correspond to the kernel running on that system.
Indeed, a valid point I did not consider.
> In the context of
> your patch, what this means is that I would prefer to have text like:
>
> [[
> The kernel source file
> .IR Documentation/admin\-guide/cgroup\-v2.rst
> (or
> .IR Documentation/admin-guide/cgroup-v2.rst in Linux x.y and earlier)
> ]]
>
> Would you be willing to revise your patch to that style?
Sure, I will prepare a new version.
Regards,
Sven
prev parent reply other threads:[~2020-06-29 20:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-19 16:35 [patch] update kernel documentation references in cgroups(7) and cpuset(7) Sven Hoexter
2020-06-29 11:40 ` Michael Kerrisk (man-pages)
2020-06-29 12:07 ` Sven Hoexter [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=20200629120759.GA14586@stormbind.net \
--to=sven@stormbind.net \
--cc=linux-man@vger.kernel.org \
--cc=mtk.manpages@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).