From: Chris Mason <chris.mason@oracle.com>
To: Tsutomu Itoh <t-itoh@jp.fujitsu.com>
Cc: Grazvydas Ignotas <notasas@gmail.com>,
linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: [PATCH] btrfs: fix directory offsets for '.' and '..' entries
Date: Sun, 18 Sep 2011 11:09:00 -0400 [thread overview]
Message-ID: <1316358521-sup-4412@shiny> (raw)
In-Reply-To: <4E6D4902.8060303@jp.fujitsu.com>
Excerpts from Tsutomu Itoh's message of 2011-09-11 19:49:22 -0400:
> The same patch has been posted about one month ago.
>
> http://marc.info/?l=linux-btrfs&m=131363399500506&w=2
Thanks, I've queued up the fujitsu version (just because they sent it
first).
-chris
prev parent reply other threads:[~2011-09-18 15:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-11 20:33 [PATCH] btrfs: fix directory offsets for '.' and '..' entries Grazvydas Ignotas
2011-09-11 21:06 ` Christoph Hellwig
2011-09-12 0:21 ` Grazvydas Ignotas
2011-09-11 23:49 ` Tsutomu Itoh
2011-09-18 15:09 ` Chris Mason [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=1316358521-sup-4412@shiny \
--to=chris.mason@oracle.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=notasas@gmail.com \
--cc=t-itoh@jp.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).