From: Robert Munteanu <robert.munteanu@gmail.com>
To: dsterba@suse.cz, Robert Munteanu <robert.munteanu@gmail.com>,
Qu Wenruo <quwenruo@cn.fujitsu.com>,
Btrfs BTRFS <linux-btrfs@vger.kernel.org>
Subject: Re: [PATCH 0/3] Fix for infinite loop on non-empty inode but with no file extent
Date: Fri, 7 Aug 2015 17:23:29 +0300 [thread overview]
Message-ID: <CAC8ULPbq1VJk0ZaGACHS9o4KnJyAf_rN1D_dikn_ExF3op6T3w@mail.gmail.com> (raw)
In-Reply-To: <20150807141908.GB10756@suse.cz>
On Fri, Aug 7, 2015 at 5:19 PM, David Sterba <dsterba@suse.cz> wrote:
> On Fri, Aug 07, 2015 at 05:17:34PM +0300, Robert Munteanu wrote:
>> Thanks for the update. Reading it looks to me like the patches should be at
>>
>> http://repo.or.cz/w/btrfs-progs-unstable/devel.git/shortlog/refs/heads/devel
>>
>> but they don't seem to be . Am I long in the wrong place again :-) ?
>
> Doh, I forgot to push the branch, sorry.
Got them now, thank you.
Robert
--
http://robert.muntea.nu/
prev parent reply other threads:[~2015-08-07 14:23 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-05 8:03 [PATCH 0/3] Fix for infinite loop on non-empty inode but with no file extent Qu Wenruo
2015-08-05 8:03 ` [PATCH 1/3] btrfs-progs: fsck: Print correct file hole Qu Wenruo
2015-08-05 8:03 ` [PATCH 2/3] btrfs-progs: fsck: Fix a infinite loop on discount file extent repair Qu Wenruo
2015-08-05 8:03 ` [PATCH 3/3] btrfs-progs: fsck-tests: Add test case for inode lost all its file extent Qu Wenruo
2015-08-05 16:40 ` [PATCH 0/3] Fix for infinite loop on non-empty inode but with no " David Sterba
2015-08-07 13:05 ` Robert Munteanu
2015-08-07 14:00 ` David Sterba
2015-08-07 14:17 ` Robert Munteanu
2015-08-07 14:19 ` David Sterba
2015-08-07 14:23 ` Robert Munteanu [this message]
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=CAC8ULPbq1VJk0ZaGACHS9o4KnJyAf_rN1D_dikn_ExF3op6T3w@mail.gmail.com \
--to=robert.munteanu@gmail.com \
--cc=dsterba@suse.cz \
--cc=linux-btrfs@vger.kernel.org \
--cc=quwenruo@cn.fujitsu.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.