From: Christoph Hellwig <hch@infradead.org>
To: "Theodore Ts'o" <tytso@mit.edu>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
linux-ext4@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [GIT PULL] ext4 bugfixes
Date: Tue, 15 Jul 2008 00:37:18 -0400 [thread overview]
Message-ID: <20080715043718.GA30017@infradead.org> (raw)
In-Reply-To: <E1KIbeO-0001yQ-N4@closure.thunk.org>
On Mon, Jul 14, 2008 at 11:56:28PM -0400, Theodore Ts'o wrote:
> Alex Tomas (2):
> vfs: add hooks for ext4's delayed allocation support
This is still missing kerneldoc comments for the newly exported
functions.
> ext4: Add delayed allocation support in data=writeback mode
And for this one I haven't even heard back on my review comments. None
of them is a merge blocker so it's not critical, but I find it quite odd
that the pull request is coming before even replying to the review
comments.
next prev parent reply other threads:[~2008-07-15 4:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-15 3:56 [GIT PULL] ext4 bugfixes Theodore Ts'o
2008-07-15 4:37 ` Christoph Hellwig [this message]
2008-07-15 12:46 ` Theodore Tso
2008-07-24 20:03 ` Christoph Hellwig
-- strict thread matches above, loose matches on Subject: below --
2008-06-06 22:17 Theodore Ts'o
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=20080715043718.GA30017@infradead.org \
--to=hch@infradead.org \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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