[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <aMGq5tNNAk5DsJWo@slm.duckdns.org>
Date: Wed, 10 Sep 2025 06:44:22 -1000
From: Tejun Heo <tj@...nel.org>
To: Jonathan Corbet <corbet@....net>
Cc: Michal Koutný <mkoutny@...e.com>,
Bagas Sanjaya <bagasdotme@...il.com>,
Mauro Carvalho Chehab <mchehab@...nel.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Linux Documentation <linux-doc@...r.kernel.org>,
Linux cgroups <cgroups@...r.kernel.org>,
Johannes Weiner <hannes@...xchg.org>,
Andrea Righi <arighi@...dia.com>,
Johannes Bechberger <me@...tlynerdless.de>,
Changwoo Min <changwoo@...lia.com>,
Shashank Balaji <shashank.mahadasyam@...y.com>,
Ingo Molnar <mingo@...nel.org>, Jake Rice <jake@...erice.dev>,
Cengiz Can <cengiz@...nel.wtf>
Subject: Re: [PATCH 2/2] Documentation: cgroup-v2: Replace manual table of
contents with contents:: directive
Hello,
On Wed, Sep 10, 2025 at 07:24:45AM -0600, Jonathan Corbet wrote:
...
> I fairly routinely get patches fixing manual TOCs that are not updated
> to match changes elsewhere. We have a nice system that can manage the
> TOC automatically for us, it seems best to me to use it.
>
> That said, if having the TOC in the plain-text version of the document
> is deemed to be important, then it needs to be kept and manually
> maintained.
Wouldn't it be better to have some automated script which triggers on
mismatching TOC so that these get fixed up. I think people (including me) do
read the plain text version, so it'd be a shame if we lose TOC in the source
file.
Thanks.
--
tejun
Powered by blists - more mailing lists