All of lore.kernel.org
 help / color / mirror / Atom feed
From: WorMzy Tykashi <wormzy.tykashi@gmail.com>
To: dsterba@suse.cz, WorMzy Tykashi <wormzy.tykashi@gmail.com>,
	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: Thu, 19 Jun 2014 08:43:36 +0100	[thread overview]
Message-ID: <CALOYprWx6OPVK=A14yRHye1x1QuTqAu1QnH74Css=vWqjDMQoQ@mail.gmail.com> (raw)
In-Reply-To: <20140618230516.GZ1903@suse.cz>

On 19 June 2014 00:05, David Sterba <dsterba@suse.cz> wrote:
> On Wed, Jun 18, 2014 at 09:59:50PM +0100, WorMzy Tykashi wrote:
>> 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.
>
> You're right, sorry. The file was not added after a conflict with
> git-am and I did not check afterwards. Local build test passed.
> Updated integration pushed, though it's a bit reduced. The 'next'
> sub-branch rebase had some suspicious glitch, I need to look closer
> tomorrow.

Thanks for the fast update. :)

Good luck battling that glitch!

Cheers,


WorMzy

  reply	other threads:[~2014-06-19  7:43 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
2014-06-18 23:05           ` David Sterba
2014-06-19  7:43             ` WorMzy Tykashi [this message]
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='CALOYprWx6OPVK=A14yRHye1x1QuTqAu1QnH74Css=vWqjDMQoQ@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.