From: Tom Talpey <tom@talpey.com>
To: Enzo Matsumiya <ematsumiya@suse.de>, Steve French <smfrench@gmail.com>
Cc: CIFS <linux-cifs@vger.kernel.org>
Subject: Re: mount.cifs man page
Date: Thu, 18 Aug 2022 13:48:01 -0400 [thread overview]
Message-ID: <f45cb6d4-d666-b4e9-adc1-705eb3bc5a1c@talpey.com> (raw)
In-Reply-To: <20220818163056.54xunvo5rfr7hi7g@cyberdelia>
On 8/18/2022 12:30 PM, Enzo Matsumiya wrote:
> On 08/18, Steve French wrote:
>> I was looking at the mount.cifs man page, which is missing
>> documentation for some mount options, and also could be made less
>> confusing by moving some of the less commonly needed mount options.
"Some" mount options?!? I counted at least 100 when I last looked
at fs_context.c ...
That said, don't let me deter you! It's a good plan.
Tom.
>> Are there good examples (of better written man pages) that we could
>> borrow ideas for a a breakdown by section, etc. ?
>
> I keep referring to nvme stuff, whether it's code or documentation. I
> think they do a pretty good job in making things clear.
>
> cf.: man 1 nvme, (e.g.) man 1 nvme-connect, drivers/nvme/*
>
> HTH
>
>> --
>> Thanks,
>>
>> Steve
>
> Cheers,
>
> Enzo
>
prev parent reply other threads:[~2022-08-18 17:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-18 16:20 mount.cifs man page Steve French
2022-08-18 16:30 ` Enzo Matsumiya
2022-08-18 17:48 ` Tom Talpey [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=f45cb6d4-d666-b4e9-adc1-705eb3bc5a1c@talpey.com \
--to=tom@talpey.com \
--cc=ematsumiya@suse.de \
--cc=linux-cifs@vger.kernel.org \
--cc=smfrench@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox