All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Sterba <dsterba@suse.cz>
To: Eric Sandeen <sandeen@redhat.com>
Cc: linux-btrfs <linux-btrfs@vger.kernel.org>, Karel Zak <kzak@redhat.com>
Subject: Re: [PATCH V2] btrfs-progs: add mount options to btrfs-mount.5
Date: Thu, 12 Jun 2014 12:51:51 +0200	[thread overview]
Message-ID: <20140612105151.GN1903@twin.jikos.cz> (raw)
In-Reply-To: <5398D4DF.9080508@redhat.com>

On Wed, Jun 11, 2014 at 05:14:55PM -0500, Eric Sandeen wrote:
> This is a straight cut and paste from the util-linux
> mount manpage into btrfs-mount.5
> 
> It's pretty much impossible for util-linux to keep up
> with every filesystem out there, and Karel has more than
> once expressed a wish that mount options move into fs-specific
> manpages.
> 
> So, here we go.
> 
> The way btrfs asciidoc is generated, there's not a trivial
> way to have both btrfs(5) and btrfs(8) so I named it btrfs-mount(5)
> for now.  A bit ick and I'm open to suggestions.

So what if the mount options are generated from btrfs-mount.txt but
installed under btrfs.5.gz name? If there are more section 5 manpages we
can make it more generic but for now hardcoding btrfs-mount.* ->
btrfs.5. sounds ok to me.

  reply	other threads:[~2014-06-12 10:51 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-11 22:13 [PATCH] btrfs-progs: add mount options to btrfs-mount.5 Eric Sandeen
2014-06-11 22:14 ` [PATCH V2] " Eric Sandeen
2014-06-12 10:51   ` David Sterba [this message]
2014-06-12 14:39     ` Eric Sandeen
2014-06-18 15:29       ` David Sterba
2014-06-18 16:18         ` Eric Sandeen
2014-06-18 20:59         ` WorMzy Tykashi
2014-06-18 23:05           ` David Sterba
2014-06-19  7:43             ` WorMzy Tykashi
2014-06-19 12:26               ` 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=20140612105151.GN1903@twin.jikos.cz \
    --to=dsterba@suse.cz \
    --cc=kzak@redhat.com \
    --cc=linux-btrfs@vger.kernel.org \
    --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 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.