From: Eric Sandeen <sandeen@redhat.com>
To: dsterba@suse.cz, 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: Wed, 18 Jun 2014 11:18:26 -0500 [thread overview]
Message-ID: <53A1BBD2.4080208@redhat.com> (raw)
In-Reply-To: <20140618152906.GW1903@twin.jikos.cz>
On 6/18/14, 10:29 AM, David Sterba wrote:
> On Thu, Jun 12, 2014 at 09:39:14AM -0500, Eric Sandeen wrote:
>>> 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.
>>
>> Yeah, that seemed like kind of nasty hard-coding, but I suppose it works
>> for now. I wanted to make it more generic, I didn't have a better idea..
>
> Added:
>
> --- a/Documentation/Makefile
> +++ b/Documentation/Makefile
> @@ -85,6 +85,9 @@ install-man: man
> $(INSTALL) -d -m 755 $(DESTDIR)$(man5dir)
> $(INSTALL) -d -m 755 $(DESTDIR)$(man8dir)
> $(INSTALL) -m 644 $(GZ_MAN5) $(DESTDIR)$(man5dir)
> + # the source file name of btrfs.5 clashes with section 8 page, but we
> + # want to keep the code generic
> + mv $(DESTDIR)$(man5dir)/btrfs-mount.5.gz $(DESTDIR)$(man5dir)/btrfs.5.gz
> $(INSTALL) -m 644 $(GZ_MAN8) $(DESTDIR)$(man8dir)
> $(LNS) btrfs-check.8.gz $(DESTDIR)$(man8dir)/btrfsck.8.gz
>
> So the MAN5 code is generic, the exception is only at the installation time.
>
Looks good to me, thanks.
-Eric
next prev parent reply other threads:[~2014-06-18 16:18 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
2014-06-12 14:39 ` Eric Sandeen
2014-06-18 15:29 ` David Sterba
2014-06-18 16:18 ` Eric Sandeen [this message]
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=53A1BBD2.4080208@redhat.com \
--to=sandeen@redhat.com \
--cc=dsterba@suse.cz \
--cc=kzak@redhat.com \
--cc=linux-btrfs@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).