From: Jonathan Corbet <corbet@lwn.net>
To: "Thorsten Leemhuis" <linux@leemhuis.info>,
"Petr Tesařík" <petr@tesarici.cz>
Cc: regressions@lists.linux.dev, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org,
Bagas Sanjaya <bagasdotme@gmail.com>,
Nathan Chancellor <nathan@kernel.org>
Subject: Re: [PATCH v1] docs: new text on bisecting which also covers bug validation
Date: Mon, 19 Feb 2024 15:12:52 -0700 [thread overview]
Message-ID: <87a5nwm7bv.fsf@meer.lwn.net> (raw)
In-Reply-To: <62ea7097-256c-4331-b937-778444125a06@leemhuis.info>
Thorsten Leemhuis <linux@leemhuis.info> writes:
> On 16.02.24 20:41, Petr Tesařík wrote:
>> Is this because you want to keep it readable if the target audience
>> reads the source text of the documentation? Otherwise, the .. include
>> directive does not make a difference after rendering to HTML. AFAIK.
>
> It less that I want that, it's more that I got the impression that both
> Jonathan and most of the kernel development community wants the source
> text to be readable; not totally sure, but I think that's the right
> thing to do, too.
As a general rule, yes. To harp on this one more time, I do think we
could create sections of the manual (a "tutorials" book, say) with a
different set of priorities.
In the documentation session at the last kernel summit, I got some
pretty clear feedback that plain-text readability could be made
secondary to getting the best rendered output, at least in some cases.
Tutorials seems like a good example of such a case, where we could focus
on good web output without, as you say, creating potential maintenance
troubles going forward.
Thanks,
jon
next prev parent reply other threads:[~2024-02-19 22:12 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-16 8:54 [PATCH v1] docs: new text on bisecting which also covers bug validation Thorsten Leemhuis
2024-02-16 19:41 ` Petr Tesařík
2024-02-17 15:46 ` Thorsten Leemhuis
2024-02-19 22:12 ` Jonathan Corbet [this message]
2024-02-20 10:28 ` Thorsten Leemhuis
2024-02-19 22:07 ` Jonathan Corbet
2024-02-20 10:26 ` Thorsten Leemhuis
2024-02-29 21:55 ` Vegard Nossum
2024-03-01 8:45 ` Thorsten Leemhuis
2024-03-03 15:35 ` Jonathan Corbet
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=87a5nwm7bv.fsf@meer.lwn.net \
--to=corbet@lwn.net \
--cc=bagasdotme@gmail.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@leemhuis.info \
--cc=nathan@kernel.org \
--cc=petr@tesarici.cz \
--cc=regressions@lists.linux.dev \
/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