Linux Btrfs filesystem development
 help / color / mirror / Atom feed
From: Karel Zak <kzak@redhat.com>
To: Eric Sandeen <sandeen@redhat.com>
Cc: Roman Mamedov <rm@romanrm.ru>, linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: [PATCH] btrfs: document mount options in Documentation/fs/btrfs.txt
Date: Tue, 26 Mar 2013 14:23:29 +0100	[thread overview]
Message-ID: <20130326132329.GC801@x2.net.home> (raw)
In-Reply-To: <514DF850.5080906@redhat.com>

On Sat, Mar 23, 2013 at 01:45:36PM -0500, Eric Sandeen wrote:
> The mount manpage is maintained in the util-linux pkg,
> but it's not kernel-version specific, and the util-linux
> maintainer does not have specific knowledge of all filesytem
> options.

Absolutely true. The util-linux maintainer is not happy that we 
don't have filesystem specific man pages for many filesystems.

The goal is to have in mount.8 only links to another man pages, for
example see smart NFS guys:

  Mount options for nfs and nfs4:
       See the options section of the nfs(5) man page (nfs-utils
       package must be installed).

  
> I think kernel docs are the right place for the developers
> to first document these things

 Definitely.

    Karel

-- 
 Karel Zak  <kzak@redhat.com>
 http://karelzak.blogspot.com

  reply	other threads:[~2013-03-26 13:23 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-23 17:48 [PATCH] btrfs: document mount options in Documentation/fs/btrfs.txt Eric Sandeen
2013-03-23 18:33 ` Roman Mamedov
2013-03-23 18:45   ` Eric Sandeen
2013-03-26 13:23     ` Karel Zak [this message]
2013-03-23 20:35 ` Ilya Dryomov
2013-03-23 22:22 ` Roger Binns
2013-03-23 22:40   ` Eric Sandeen
2013-03-24  1:11     ` Roger Binns
2013-03-25 15:57       ` David Sterba
2013-03-25 13:59   ` Josef Bacik
2013-03-26 19:36 ` [PATCH V2] " Eric Sandeen
2013-03-29 16:48   ` David Sterba

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=20130326132329.GC801@x2.net.home \
    --to=kzak@redhat.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=rm@romanrm.ru \
    --cc=sandeen@redhat.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