From: Markus Heiser <markus.heiser@darmarit.de>
To: Amol Grover <frextrite@gmail.com>,
amanharitsh123 <amanharitsh123@gmail.com>
Cc: "Paul E. McKenney" <paulmck@kernel.org>,
Jonathan Corbet <corbet@lwn.net>,
linux-doc@vger.kernel.org, Lai Jiangshan <jiangshanlai@gmail.com>,
Josh Triplett <josh@joshtriplett.org>,
Steven Rostedt <rostedt@goodmis.org>,
linux-kernel@vger.kernel.org, rcu@vger.kernel.org,
Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
Joel Fernandes <joel@joelfernandes.org>,
linux-kernel-mentees@lists.linuxfoundation.org
Subject: Re: [Linux-kernel-mentees] [PATCH] doc: Convert to checklist.txt to checklist.rst
Date: Thu, 27 Feb 2020 09:47:45 +0100 [thread overview]
Message-ID: <c844ac77-4841-3454-dc92-5af0c9800a22@darmarit.de> (raw)
In-Reply-To: <20200227083010.GB5241@workstation-portable>
Am 27.02.20 um 09:30 schrieb Amol Grover:
>> diff --git a/Documentation/RCU/checklist.txt b/Documentation/RCU/checklist.rst
>> similarity index 99%
>> rename from Documentation/RCU/checklist.txt
>> rename to Documentation/RCU/checklist.rst
>> index e98ff261a438..49bf7862c950 100644
>> --- a/Documentation/RCU/checklist.txt
>> +++ b/Documentation/RCU/checklist.rst
>> @@ -1,5 +1,7 @@
>> -Review Checklist for RCU Patches
>> +.. checklist doc:
> 2. The document identifier must always start with an underscore and
> should not contain white spaces, something like:
> .. _checklist_doc:
> should work.
>
Sphinx supports whitespaces in anchor names, see by example [1]
[1] https://asciimoo.github.io/searx/dev/reST.html#anchors-links
-- Markus --
next prev parent reply other threads:[~2020-02-27 8:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-25 18:39 [PATCH] doc: Convert to checklist.txt to checklist.rst amanharitsh123
2020-02-27 8:30 ` [Linux-kernel-mentees] " Amol Grover
2020-02-27 8:47 ` Markus Heiser [this message]
2020-02-27 9:08 ` [Linux-kernel-mentees] [PATCH v2] " Aman Sharma
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=c844ac77-4841-3454-dc92-5af0c9800a22@darmarit.de \
--to=markus.heiser@darmarit.de \
--cc=amanharitsh123@gmail.com \
--cc=corbet@lwn.net \
--cc=frextrite@gmail.com \
--cc=jiangshanlai@gmail.com \
--cc=joel@joelfernandes.org \
--cc=josh@joshtriplett.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel-mentees@lists.linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=paulmck@kernel.org \
--cc=rcu@vger.kernel.org \
--cc=rostedt@goodmis.org \
/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;
as well as URLs for NNTP newsgroup(s).