From: Karel Zak <kzak@redhat.com>
To: Gui Hecheng <guihc.fnst@cn.fujitsu.com>
Cc: util-linux@vger.kernel.org, linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: [PATCH] mount: add btrfs to mount.8
Date: Fri, 6 Jun 2014 11:44:28 +0200 [thread overview]
Message-ID: <20140606094428.GA30975@x2.net.home> (raw)
In-Reply-To: <1402036359.17740.33.camel@localhost.localdomain>
On Fri, Jun 06, 2014 at 02:32:39PM +0800, Gui Hecheng wrote:
> But for now, there are btrfs *users* complaining that they cannot find
> any help by refering to the mount manpage when they want to mount their
> btrfs. Actually, not every btrfs user have the mood to check the
> Documentation/filesystems/btrfs.txt or anywhere else when they just want
> to use a simple mount cmd.
The kernel is the "ideal place", but it's more dream than anything
else... what we use for example for NFS is to maintain FS specific
man page in userspace FS package (e.g. nfs-utils).
Wouldn't be possible to add the man page to btrfs-progs package? The
package is maintained by btrfs guys and I guess all btrfs users have
very probably installed the package.
> So, If it does not bother you much...
I personally have no problem to maintain information about arbitrary
FS in mount.8, the problem are updates. Unfortunately, kernel FS developers
don't care about the man page at all and it's very often not up to date.
[My experience is very bad. Not sure why, but for many kernel devels
commit into Linus' tree is end of their work, they don't care if there
is usable userpsace util or docs for users, people like Eric Biederman
or Lukas Czerner are rare exception.]
> And I think there are many btrfs developers who will be
> glad to continue helping correct the btrfs part.
OK, we can try it, if you still prefer mount.8.
Karel
--
Karel Zak <kzak@redhat.com>
http://karelzak.blogspot.com
next prev parent reply other threads:[~2014-06-06 9:44 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-05 2:05 [PATCH] mount: add btrfs to mount.8 Gui Hecheng
2014-06-05 8:03 ` Karel Zak
2014-06-06 6:32 ` Gui Hecheng
2014-06-06 9:44 ` Karel Zak [this message]
2014-06-06 10:02 ` Gui Hecheng
2014-06-06 10:03 ` Karel Zak
2014-06-06 10:03 ` Gui Hecheng
2014-06-06 15:52 ` Eric Sandeen
2014-06-07 13:41 ` Christoph Hellwig
2014-06-09 14:09 ` Eric Sandeen
2014-06-09 14:22 ` Karel Zak
2014-06-11 22:09 ` Eric Sandeen
2014-06-06 10:17 ` Karel Zak
2014-06-09 6:26 ` Gui Hecheng
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=20140606094428.GA30975@x2.net.home \
--to=kzak@redhat.com \
--cc=guihc.fnst@cn.fujitsu.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=util-linux@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).