From: Matthew Wilcox <willy@infradead.org>
To: Mr Tourist <zakiuddin321@gmail.com>
Cc: linux-doc@vger.kernel.org
Subject: Re: [PATCH] docs: reorganize kernel documentation overview for clarity
Date: Thu, 2 Oct 2025 02:12:47 +0100 [thread overview]
Message-ID: <aN3RjymBjn_VfcLe@casper.infradead.org> (raw)
In-Reply-To: <CAOXP31GrRf2Q8NcqQ4161TiUuagZjp8i6CmEPZC1LsiGjxcD2Q@mail.gmail.com>
On Wed, Oct 01, 2025 at 04:50:52PM +0530, Mr Tourist wrote:
... you screwed up sending this, so I can't reply to it properly.
But in general, Linux uses reStructuredText, not Markdown.
next prev parent reply other threads:[~2025-10-02 1:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-01 11:20 [PATCH] docs: reorganize kernel documentation overview for clarity Mr Tourist
2025-10-01 17:26 ` Randy Dunlap
2025-10-02 1:12 ` Matthew Wilcox [this message]
2025-10-02 4:16 ` Mr Tourist
2025-10-02 12:23 ` Matthew Wilcox
2025-10-02 12:26 ` Bagas Sanjaya
2025-10-03 14:25 ` 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=aN3RjymBjn_VfcLe@casper.infradead.org \
--to=willy@infradead.org \
--cc=linux-doc@vger.kernel.org \
--cc=zakiuddin321@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