From: "Daniel W. S. Almeida" <dwlsalmeida@gmail.com>
To: Markus Heiser <markus.heiser@darmarit.de>,
corbet@lwn.net, miklos@szeredi.hu
Cc: linux-fsdevel@vger.kernel.org,
linux-kernel-mentees@lists.linuxfoundation.org,
linux-kernel@vger.kernel.org, linux-doc@vger.kernel.org
Subject: Re: [Linux-kernel-mentees] [PATCH v3] Documentation: filesystems: convert fuse to RST
Date: Tue, 24 Dec 2019 15:27:02 -0300 [thread overview]
Message-ID: <021221ea-9e1d-78ed-3ca9-dea232e0cddd@gmail.com> (raw)
In-Reply-To: <91ded87c-ca70-bcf7-49fc-fa2988f4e36b@darmarit.de>
[-- Attachment #1.1: Type: text/plain, Size: 652 bytes --]
Hi Markus!
> drop empty line, use definition list[1] / you used definition list
> everywhere except here. I guess the follwowing matches better:
>
>
> ``fuse``
> This is the usual way to mount a FUSE filesystem. ...
>
> ``fuseblk``
> The filesystem is block device based. ..
>
> [1]
> https://docutils.sourceforge.io/docs/ref/rst/restructuredtext.html#definition-lists
>
>
> -- Markus --
To be honest I had not realized that! Good catch!
Also, do you mean it would be better to switch the terms from **term**
to ``term`` in all the other definition lists as well?
[note: pardon me for the duplicate email...forgot to 'reply to all']
[-- Attachment #1.2: Type: text/html, Size: 1204 bytes --]
[-- Attachment #2: Type: text/plain, Size: 201 bytes --]
_______________________________________________
Linux-kernel-mentees mailing list
Linux-kernel-mentees@lists.linuxfoundation.org
https://lists.linuxfoundation.org/mailman/listinfo/linux-kernel-mentees
prev parent reply other threads:[~2019-12-24 18:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-23 1:22 [Linux-kernel-mentees] [PATCH v3] Documentation: filesystems: convert fuse to RST Daniel W. S. Almeida
2019-12-23 7:37 ` Markus Heiser
2019-12-24 18:27 ` Daniel W. S. Almeida [this message]
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=021221ea-9e1d-78ed-3ca9-dea232e0cddd@gmail.com \
--to=dwlsalmeida@gmail.com \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel-mentees@lists.linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=markus.heiser@darmarit.de \
--cc=miklos@szeredi.hu \
/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).