On 21/04/2020 18:23, Christoph Hellwig wrote:
It wasn't entirely uncommon, but that's not really the point. The Problem is all the weird ".." or "::" annotations that really kill the flow, or things like "|copy|" that have no reason to exist.
You aren't supposed to read REST documentation files - as opposed to kerneldoc comments in the C source - any more than you read HTML.
[ Exactly what should or should not be in C source kerneldoc is another matter. ]
Developers are used to reading plain ol' text files for quick reference. But there is no make target to generate the text files.
Can we create a method to build text *output* files?
