From: Miklos Szeredi <miklos@szeredi.hu>
To: "Daniel W. S. Almeida" <dwlsalmeida@gmail.com>
Cc: linux-doc@vger.kernel.org, Jonathan Corbet <corbet@lwn.net>,
linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org,
linux-kernel-mentees@lists.linuxfoundation.org
Subject: Re: [Linux-kernel-mentees] [PATCH v2] Documentation: filesystems: convert fuse to RST
Date: Mon, 25 Nov 2019 11:41:57 +0100 [thread overview]
Message-ID: <CAJfpegsxXJN1Z5fGzcv=+sid6gSzyD=KtA2omF2Xsx8dy00tRw@mail.gmail.com> (raw)
In-Reply-To: <20191120192655.33709-1-dwlsalmeida@gmail.com>
On Wed, Nov 20, 2019 at 8:34 PM Daniel W. S. Almeida
<dwlsalmeida@gmail.com> wrote:
>
> From: "Daniel W. S. Almeida" <dwlsalmeida@gmail.com>
>
>
> Converts fuse.txt to reStructuredText format, improving the presentation
> without changing much of the underlying content.
Hmm, most of this document is *not* an admin-guide at all. The only
sections that really belong in that category are "What is FUSE?" and
"Control filesystem" and maybe some of the definitions as well. The
mount options for fuse filesystem are not generally usable for
actually performing a mount, most of those are actually internal
details of the filesystem implementation.
So I suggest leaving this file under Documentation/filesystems/ for
now and later work towards splitting out the admin-guide parts into a
separate document.
Thanks,
Miklos
_______________________________________________
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-11-25 10:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-20 19:26 [Linux-kernel-mentees] [PATCH v2] Documentation: filesystems: convert fuse to RST Daniel W. S. Almeida
2019-11-25 10:41 ` Miklos Szeredi [this message]
2019-11-30 4:58 ` Daniel W. S. Almeida
2019-12-19 16:53 ` Jonathan Corbet
2019-12-19 17:01 ` 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='CAJfpegsxXJN1Z5fGzcv=+sid6gSzyD=KtA2omF2Xsx8dy00tRw@mail.gmail.com' \
--to=miklos@szeredi.hu \
--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 \
/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).