From: Markus Heiser <markus.heiser@darmarit.de>
To: "Daniel W. S. Almeida" <dwlsalmeida@gmail.com>,
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: Mon, 23 Dec 2019 08:37:33 +0100 [thread overview]
Message-ID: <91ded87c-ca70-bcf7-49fc-fa2988f4e36b@darmarit.de> (raw)
In-Reply-To: <20191223012248.606168-1-dwlsalmeida@gmail.com>
Hi Daniel,
just some nits ...
Am 23.12.19 um 02:22 schrieb Daniel W. S. Almeida:
> From: "Daniel W. S. Almeida" <dwlsalmeida@gmail.com>
...
> diff --git a/Documentation/filesystems/fuse.txt b/Documentation/filesystems/fuse.rst
> similarity index 79%
> rename from Documentation/filesystems/fuse.txt
> rename to Documentation/filesystems/fuse.rst
> index 13af4a49e7db..1ca3aac04606 100644
> --- a/Documentation/filesystems/fuse.txt
> +++ b/Documentation/filesystems/fuse.rst
> @@ -1,41 +1,39 @@
...
> Filesystem type
> -~~~~~~~~~~~~~~~
> +===============
>
> The filesystem type given to mount(2) can be one of the following:
>
> -'fuse'
> + **fuse**
>
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 --
_______________________________________________
Linux-kernel-mentees mailing list
Linux-kernel-mentees@lists.linuxfoundation.org
https://lists.linuxfoundation.org/mailman/listinfo/linux-kernel-mentees
next prev parent reply other threads:[~2019-12-23 7:47 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 [this message]
2019-12-24 18:27 ` Daniel W. S. Almeida
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=91ded87c-ca70-bcf7-49fc-fa2988f4e36b@darmarit.de \
--to=markus.heiser@darmarit.de \
--cc=corbet@lwn.net \
--cc=dwlsalmeida@gmail.com \
--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=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).