From: "Holger Hoffstätte" <holger@applied-asynchrony.com>
To: linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: kdave/for-next commit 26112f7f472
Date: Fri, 8 Jul 2016 14:31:27 +0200 [thread overview]
Message-ID: <577F9D1F.8050400@applied-asynchrony.com> (raw)
In-Reply-To: <fd43645d-fac7-faf9-565f-dfbc6a84ecf5@suse.com>
[-- Attachment #1.1: Type: text/plain, Size: 558 bytes --]
On 07/08/16 13:55, Jeff Mahoney wrote:
> On 7/8/16 7:19 AM, Holger Hoffstätte wrote:
>> On 07/08/16 06:24, Jeff Mahoney wrote:
>>> Hi Dave -
>>>
>>> This commit introduces a bug. I ran across it when running xfstests
>>> against my own integrated branch.
>>
>> I can't find that commit id anywhere...?
>
> Hi Holger -
>
> This is the for-next branch. It's not in any mainline branch yet.
Yes, I understand that. I searched in the github/kdave tree, which only
has the for-next-xyz branches. Found it in the one on kernel.org.
-h
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 226 bytes --]
next prev parent reply other threads:[~2016-07-08 12:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-08 4:24 kdave/for-next commit 26112f7f472 Jeff Mahoney
2016-07-08 11:19 ` Holger Hoffstätte
2016-07-08 11:55 ` Jeff Mahoney
2016-07-08 12:31 ` Holger Hoffstätte [this message]
2016-07-08 13:37 ` 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=577F9D1F.8050400@applied-asynchrony.com \
--to=holger@applied-asynchrony.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