From: Jonathan Corbet <corbet@lwn.net>
To: Osman Ahmadzai <osmanahmadxai@gmail.com>
Cc: linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] README: add a reST version with clickable documentation links
Date: Sun, 20 Sep 2026 23:47:08 -0600 [thread overview]
Message-ID: <87o6dryx43.fsf@trenco.lwn.net> (raw)
In-Reply-To: <20260921050038.76985-1-osmanahmadxai@gmail.com>
Osman Ahmadzai <osmanahmadxai@gmail.com> writes:
> The README points at some sixty files in the tree, but it has no
> extension, so it shows up as plain text and none of those paths can be
> followed. You have to go and find each one by hand.
>
> Add README.rst with the same content, wrapping each path in an anonymous
> reST reference. The link text is the path itself, so the file reads the
> same as it does now. Anonymous because a handful of the paths are listed
> twice and named targets would collide.
>
> README itself is left alone - checkpatch.pl and get_maintainer.pl both
> look for a file called README to find the top of the tree, and the
> Makefile points at it too, so renaming would mean touching all three.
>
> Signed-off-by: Osman Ahmadzai <osmanahmadxai@gmail.com>
Creating a second file with duplicated content isn't really going to
help...they'll be out of sync within one release cycle. Better to have
a single file and use a symlink (or else to simply rename it and fix the
other files as well). Or, perhaps best yet, see if it can be integrated
with Documentation/index.rst.
Thanks,
jon
next prev parent reply other threads:[~2026-09-21 5:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-21 5:00 Osman Ahmadzai
2026-09-21 5:47 ` Jonathan Corbet [this message]
2026-09-21 7:05 ` [PATCH v2] README: rename to README.rst and make the doc references links Osman Ahmadzai
2026-09-21 19:24 ` Randy Dunlap
2026-09-21 19:36 ` Matthew Wilcox
2026-09-21 20:14 ` Randy Dunlap
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=87o6dryx43.fsf@trenco.lwn.net \
--to=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=osmanahmadxai@gmail.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
all inboxes | Powered by JetHome®