From: Jonathan Corbet <corbet@lwn.net>
To: Nishanth Menon <nm@ti.com>, Mauro Carvalho Chehab <mchehab@kernel.org>
Cc: linux-kernel@vger.kernel.org, linux-doc@vger.kernel.org,
bpf@vger.kernel.org,
Heinrich Schuchardt <heinrich.schuchardt@canonical.com>,
Mattijs Korpershoek <mkorpershoek@baylibre.com>,
Simon Glass <sjg@chromium.org>, Tom Rini <trini@konsulko.com>,
Neha Francis <n-francis@ti.com>, Nishanth Menon <nm@ti.com>
Subject: Re: [PATCH 1/2] Documentation: sphinx: Add sphinx-prompt
Date: Fri, 25 Aug 2023 16:46:07 -0600 [thread overview]
Message-ID: <87h6om4u6o.fsf@meer.lwn.net> (raw)
In-Reply-To: <20230824182107.3702766-2-nm@ti.com>
Nishanth Menon <nm@ti.com> writes:
> Sphinx-prompt[1] helps bring-in '.. prompt::' option that allows a
> better rendered documentation, yet be able to copy paste without
> picking up the prompt from the rendered documentation.
>
> [1] https://pypi.org/project/sphinx-prompt/
> Link: https://lore.kernel.org/all/87fs48rgto.fsf@baylibre.com/
> Suggested-by: Mattijs Korpershoek <mkorpershoek@baylibre.com>
> Suggested-by: Heinrich Schuchardt <heinrich.schuchardt@canonical.com>
> Signed-off-by: Nishanth Menon <nm@ti.com>
> ---
> I would have added Reported-by for Simon, since he reported the issue in
> the first place.. but it was for the u-boot documentation, so skipping
> here.
>
> Documentation/conf.py | 2 +-
> Documentation/sphinx/requirements.txt | 1 +
> 2 files changed, 2 insertions(+), 1 deletion(-)
So it would sure be nice for the changelog to say what this actually
does.
This appears to add a build dependency for the docs; we can't just add
that without updating the documentation, adjusting
scripts/sphinx-pre-install, and so on.
But, beyond that, this extension goes entirely counter to the idea that
the plain-text files are the primary form of documentation; it adds
clutter and makes those files less readable. We can do that when the
benefit is sufficient, but I'm pretty far from convinced that this is
the case here. Certainly the case hasn't been made in the changelog.
What *is* the benefit of making this change?
Thanks,
jon
next prev parent reply other threads:[~2023-08-25 22:47 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-24 18:21 [PATCH 0/2] Documentation: sphinx: Add sphinx-prompt Nishanth Menon
2023-08-24 18:21 ` [PATCH 1/2] " Nishanth Menon
2023-08-25 14:16 ` Daniel Borkmann
2023-08-25 22:46 ` Jonathan Corbet [this message]
2023-08-28 12:59 ` Nishanth Menon
2023-08-28 13:41 ` Jonathan Corbet
2023-08-28 13:51 ` Nishanth Menon
2023-08-28 14:09 ` Matthew Wilcox
2023-08-28 15:12 ` Jonathan Corbet
2023-08-28 17:25 ` Mauro Carvalho Chehab
2023-08-28 18:37 ` Jonathan Corbet
2023-08-24 18:21 ` [PATCH 2/2] Documentation: bpf: Use sphinx-prompt Nishanth Menon
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=87h6om4u6o.fsf@meer.lwn.net \
--to=corbet@lwn.net \
--cc=bpf@vger.kernel.org \
--cc=heinrich.schuchardt@canonical.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=mkorpershoek@baylibre.com \
--cc=n-francis@ti.com \
--cc=nm@ti.com \
--cc=sjg@chromium.org \
--cc=trini@konsulko.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