From: Federico Vaga <federico.vaga@vaga.pv.it>
To: Jonathan Corbet <corbet@lwn.net>, linux-doc@vger.kernel.org
Subject: [INFO] Documentation/RCU ReST format
Date: Mon, 27 Apr 2020 00:23:08 +0200 [thread overview]
Message-ID: <2106522.Q2ZRUUiV7S@harkonnen> (raw)
Hi,
is there a reason for not converting the .txt files in Documentation/RCU?
next reply other threads:[~2020-04-26 22:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-26 22:23 Federico Vaga [this message]
2020-04-26 22:36 ` [INFO] Documentation/RCU ReST format Randy Dunlap
2020-04-27 7:07 ` Federico Vaga
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=2106522.Q2ZRUUiV7S@harkonnen \
--to=federico.vaga@vaga.pv.it \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.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).