All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Daniel W. S. Almeida" <dwlsalmeida@gmail.com>
To: Jonathan Corbet <corbet@lwn.net>
Cc: miklos@szeredi.hu, linux-doc@vger.kernel.org,
	linux-kernel@vger.kernel.org, skhan@linuxfoundation.org,
	linux-kernel-mentees@lists.linuxfoundation.org,
	linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH v2] Documentation: filesystems: convert fuse to RST
Date: Thu, 19 Dec 2019 14:01:58 -0300	[thread overview]
Message-ID: <2eba770a-f566-d704-35b3-7c00995bbc76@gmail.com> (raw)
In-Reply-To: <20191219095356.4a3ad965@lwn.net>

Hey Jonathan! I hope you're doing fine.


> So I have to confess that I've lost track of where we stand with this.
> Holidays and moving house will do that...apologies.  In any case, I have a
> couple of additional comments.


Actually Miklos replied. While he did not comment on the amount of 
markup used, he had this to add:

> 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.

Please let me know what you think? I can do another pass to clean this 
up and remove more markup, no problem!


-Daniel.


WARNING: multiple messages have this Message-ID (diff)
From: "Daniel W. S. Almeida" <dwlsalmeida@gmail.com>
To: Jonathan Corbet <corbet@lwn.net>
Cc: linux-doc@vger.kernel.org, miklos@szeredi.hu,
	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: Thu, 19 Dec 2019 14:01:58 -0300	[thread overview]
Message-ID: <2eba770a-f566-d704-35b3-7c00995bbc76@gmail.com> (raw)
In-Reply-To: <20191219095356.4a3ad965@lwn.net>

Hey Jonathan! I hope you're doing fine.


> So I have to confess that I've lost track of where we stand with this.
> Holidays and moving house will do that...apologies.  In any case, I have a
> couple of additional comments.


Actually Miklos replied. While he did not comment on the amount of 
markup used, he had this to add:

> 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.

Please let me know what you think? I can do another pass to clean this 
up and remove more markup, no problem!


-Daniel.

_______________________________________________
Linux-kernel-mentees mailing list
Linux-kernel-mentees@lists.linuxfoundation.org
https://lists.linuxfoundation.org/mailman/listinfo/linux-kernel-mentees

  reply	other threads:[~2019-12-19 17:02 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-20 19:26 [PATCH v2] Documentation: filesystems: convert fuse to RST Daniel W. S. Almeida
2019-11-20 19:26 ` [Linux-kernel-mentees] " Daniel W. S. Almeida
2019-11-25 10:41 ` Miklos Szeredi
2019-11-25 10:41   ` [Linux-kernel-mentees] " Miklos Szeredi
2019-11-30  4:58   ` Daniel W. S. Almeida
2019-11-30  4:58     ` [Linux-kernel-mentees] " Daniel W. S. Almeida
2019-12-19 16:53 ` Jonathan Corbet
2019-12-19 16:53   ` [Linux-kernel-mentees] " Jonathan Corbet
2019-12-19 17:01   ` Daniel W. S. Almeida [this message]
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=2eba770a-f566-d704-35b3-7c00995bbc76@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=miklos@szeredi.hu \
    --cc=skhan@linuxfoundation.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.