All of lore.kernel.org
 help / color / mirror / Atom feed
From: WorMzy Tykashi <wormzy.tykashi@gmail.com>
To: dsterba@suse.cz, Eric Sandeen <sandeen@redhat.com>,
	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 21:59:50 +0100	[thread overview]
Message-ID: <CALOYprVo60UrZWWVk34MDur6CpDAG2a1Cg3cWd0M__gWKnQywA@mail.gmail.com> (raw)
In-Reply-To: <20140618152906.GW1903@twin.jikos.cz>

On 18 June 2014 16:29, David Sterba <dsterba@suse.cz> 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.
> --
> To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

Hi David,

I think you forgot to apply the patch that adds
Documentation/btrfs-mount.5.txt before you tagged
integration-20140618, man5 (and consequently Documentation) can't be
made without it, causing a failed build.

make: *** No rule to make target 'btrfs-mount.5.gz', needed by 'man5'.  Stop.

Any chance of a quick fix and a -2 tag?

Cheers,


WorMzy

  parent reply	other threads:[~2014-06-18 20:59 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
2014-06-18 20:59         ` WorMzy Tykashi [this message]
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=CALOYprVo60UrZWWVk34MDur6CpDAG2a1Cg3cWd0M__gWKnQywA@mail.gmail.com \
    --to=wormzy.tykashi@gmail.com \
    --cc=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.