From: Naohiro Aota <naota@elisp.net>
To: "linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>
Cc: Naohiro Aota <naota@elisp.net>, David Sterba <dsterba@suse.cz>,
Qu Wenruo <quwenruo.btrfs@gmx.com>
Subject: Re: [PATCH 0/3] btrfs-progs: fix file restore to lost+found bug
Date: Tue, 8 Dec 2015 11:06:28 +0900 [thread overview]
Message-ID: <CAEe67=8JC38S_eNenwg2QmcMLKetR3zbzj0aMTXGcV4U1gCBzQ@mail.gmail.com> (raw)
In-Reply-To: <20151207153538.GG4227@twin.jikos.cz>
On Tue, Dec 8, 2015 at 12:35 AM, David Sterba <dsterba@suse.cz> wrote:
> On Mon, Dec 07, 2015 at 11:59:19AM +0900, Naohiro Aota wrote:
>> > But I only see the first 2 patches in maillist...
>> > The last test case seems missing?
>>
>> Maybe, the last patch is too large to post to the list? Even it get
>> smaller, 130260 bytes seems to be a bit large.
>>
>> How should I handle this? Put my repo somewhere and wait a maintainer
>> to pull it?
>
> Please send it to me directly. The image will be available in
> btrfs-progs git and we don't necessarily need the copy in the
> mailinglist.
Sure. I'll send it to you.
next prev parent reply other threads:[~2015-12-08 2:06 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-04 5:37 [PATCH 0/3] btrfs-progs: fix file restore to lost+found bug Naohiro Aota
2015-12-04 5:37 ` [PATCH 1/3] btrfs-progs: test: umount if confirmation failed Naohiro Aota
2015-12-07 15:33 ` David Sterba
2015-12-08 2:18 ` Naohiro Aota
2015-12-04 5:37 ` [PATCH 2/3] btrfs-progs: properly reset nlink of multi-linked file Naohiro Aota
2015-12-05 1:34 ` Qu Wenruo
2015-12-07 15:37 ` David Sterba
2015-12-05 1:35 ` [PATCH 0/3] btrfs-progs: fix file restore to lost+found bug Qu Wenruo
2015-12-07 2:59 ` Naohiro Aota
2015-12-07 3:02 ` Qu Wenruo
2015-12-07 15:35 ` David Sterba
2015-12-08 2:06 ` Naohiro Aota [this message]
2015-12-15 10:13 ` 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='CAEe67=8JC38S_eNenwg2QmcMLKetR3zbzj0aMTXGcV4U1gCBzQ@mail.gmail.com' \
--to=naota@elisp.net \
--cc=dsterba@suse.cz \
--cc=linux-btrfs@vger.kernel.org \
--cc=quwenruo.btrfs@gmx.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.