All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bagas Sanjaya <bagasdotme@gmail.com>
To: Seamus de Mora <seamusdemora@gmail.com>,
	Linux Manual Pages <linux-man@vger.kernel.org>,
	Linux Filesystems Development <linux-fsdevel@vger.kernel.org>
Cc: Alejandro Colomar <alx@kernel.org>,
	Namjae Jeon <linkinjeon@kernel.org>,
	Sungjong Seo <sj1557.seo@samsung.com>
Subject: Re: Add sub-topic on 'exFAT' in man mount
Date: Tue, 21 Nov 2023 13:55:25 +0700	[thread overview]
Message-ID: <ZVxUXZrlIaRJKghT@archie.me> (raw)
In-Reply-To: <CAJ8C1XPdyVKuq=cL4CqOi2+ag-=tEbaC=0a3Zro9ZZU5Xw1cjw@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 996 bytes --]

On Mon, Nov 20, 2023 at 04:55:18PM -0600, Seamus de Mora wrote:
> I'd like to volunteer to add some information to the mount manual.
> 
> I'm told that exFAT was added to the kernel about 4 years ago, but
> last I checked, there was nothing about it in man mount.  I feel this
> could be addressed best by adding a sub-topic on exFAT under the topic
> `FILESYSTEM-SPECIFIC MOUNT OPTIONS`.
> 
> If my application is of interest, please let me know what steps I need
> to take - or how to approach this task.
> 

I'm adding from Alejandro's reply.

You can start reading the source in fs/exfat in linux.git tree [1].
Then you can write the documentation for exfat in Documentation/exfat.rst
(currently doesn't exist yet), at the same time of your manpage contribution.

Cc'ing exfat maintainers for better treatment.

Thanks.

[1]: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/fs/exfat

-- 
An old man doll... just what I always wanted! - Clara

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]

  parent reply	other threads:[~2023-11-21  6:55 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-20 22:55 Add sub-topic on 'exFAT' in man mount Seamus de Mora
2023-11-20 23:33 ` Alejandro Colomar
2023-11-20 23:44   ` Seamus de Mora
2023-11-21  6:48     ` Bagas Sanjaya
2023-11-21 10:08       ` Alejandro Colomar
2023-11-21 11:41         ` Bagas Sanjaya
2023-11-21 12:51           ` Alejandro Colomar
2023-11-21 13:57             ` Bagas Sanjaya
2023-11-21 13:55         ` G. Branden Robinson
2023-11-21 16:41       ` Seamus de Mora
2023-11-21  6:55 ` Bagas Sanjaya [this message]
2023-11-26 23:59   ` Namjae Jeon
2023-11-27 22:43     ` Seamus de Mora
2023-12-05  7:49       ` Seamus de Mora
2023-12-05  9:03         ` Bagas Sanjaya

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=ZVxUXZrlIaRJKghT@archie.me \
    --to=bagasdotme@gmail.com \
    --cc=alx@kernel.org \
    --cc=linkinjeon@kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-man@vger.kernel.org \
    --cc=seamusdemora@gmail.com \
    --cc=sj1557.seo@samsung.com \
    /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.