linux-kernel - Re: [PATCH v3] Documentation: cgroup-v2: Replace manual table of contents with contents:: directive

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <aMwsZism0R-ZHLkq@slm.duckdns.org>
Date: Thu, 18 Sep 2025 05:59:34 -1000
From: Tejun Heo <tj@...nel.org>
To: Michal Koutný <mkoutny@...e.com>
Cc: Bagas Sanjaya <bagasdotme@...il.com>,
	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>,
	Jonathan Corbet <corbet@....net>
Subject: Re: [PATCH v3] Documentation: cgroup-v2: Replace manual table of
 contents with contents:: directive

Hello,

On Thu, Sep 18, 2025 at 05:55:07PM +0200, Michal Koutný wrote:
> On Thu, Sep 18, 2025 at 05:44:56AM -1000, Tejun Heo <tj@...nel.org> wrote:
> > I don't think I'm going to apply this. Sure, it can get out of sync but I'd
> > rather have TOC which sometimes is a bit out of sync than none at all.
> 
> The TOC is in the generated output :-p

I know it's tongue-in-cheek but one big benefit of the doc format we use is
that these are still very readable as a plain text document. In general, I
don't want to make changes that worsens plain text accessibility.

> I understand you want this "[PATCH v2 4/4] Documentation: cgroup-v2: Sync
> manual toctree" [1], which is also fine.
> But I'd drop this "[PATCH v2 2/4] Documentation: cgroup-v2: Add section
> numbers" [2], because that adds more places for out-of-syncness.
> 
> [1] https://lore.kernel.org/lkml/20250915081942.25077-5-bagasdotme@gmail.com/
> [2] https://lore.kernel.org/lkml/20250915081942.25077-3-bagasdotme@gmail.com/

Sure, that makes sense. Will apply [1].

Thanks

---
tejun

Thank.s

-- 
tejun