From: "Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com>
To: "Theodore Ts'o" <tytso@mit.edu>
Cc: linux-ext4@vger.kernel.org
Subject: Re: [GIT PULL] ext4 for v2.6.32
Date: Fri, 25 Sep 2009 13:31:35 +0530 [thread overview]
Message-ID: <20090925080135.GA15586@skywalker.linux.vnet.ibm.com> (raw)
In-Reply-To: <E1MohbG-0006qg-1y@closure.thunk.org>
On Fri, Sep 18, 2009 at 01:50:26PM -0400, Theodore Ts'o wrote:
> Hi Linus,
>
> Please pull from:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/tytso/ext4.git for_linus
>
> to grab the following changes for v2.6.32.
.....
....
>
> Frank Mayhar (1):
> ext4: Make non-journal fsync work properly
>
I had a review comment on this patch
http://article.gmane.org/gmane.comp.file-systems.ext4/15498
Frank agreed to send an updated patch
http://article.gmane.org/gmane.comp.file-systems.ext4/15499
But the comment is not critical. So should we do a new patch as a cleanup
or leave the change as it is now ?
-aneesh
prev parent reply other threads:[~2009-09-25 8:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-18 17:50 [GIT PULL] ext4 for v2.6.32 Theodore Ts'o
2009-09-25 8:01 ` Aneesh Kumar K.V [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=20090925080135.GA15586@skywalker.linux.vnet.ibm.com \
--to=aneesh.kumar@linux.vnet.ibm.com \
--cc=linux-ext4@vger.kernel.org \
--cc=tytso@mit.edu \
/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).