From: tristan <tristan.ye@oracle.com>
To: ocfs2-devel@oss.oracle.com
Subject: [Ocfs2-devel] [PATCH 0/4] Patches series for optimization of truncating and punching-hole.
Date: Tue, 11 May 2010 09:27:51 +0800 [thread overview]
Message-ID: <4BE8B297.30708@oracle.com> (raw)
In-Reply-To: <20100510194744.GB2836@mail.oracle.com>
Joel Becker wrote:
> On Thu, May 06, 2010 at 03:04:48PM +0800, tristan wrote:
>> Following 4 patches are the entire patches series of truncating and
>> punching-holes atop your latest merge-window branch.
>>
>> And it survived all my testcases on hand.
>
> Tristan,
> Thank you for sending the new series. It looks good
> functionally. I replied to the first patch with a couple of cleanups.
All cleanups make sense!
> Please use the --compose option to git-send-email to create your
> [PATCH 0/x] emails. This makes them thread in our mailboxes better ;-)
Joel,
Thank you for teaching me this, it really helps, I usually hand-edit the
[patch 0/x] before;-(
> Mark, can I get your evaluation of this patch series before I
> push it to merge-window?
>
> Joel
>
next prev parent reply other threads:[~2010-05-11 1:27 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-06 7:04 [Ocfs2-devel] [PATCH 0/4] Patches series for optimization of truncating and punching-hole tristan
2010-05-10 19:47 ` Joel Becker
2010-05-11 1:27 ` tristan [this message]
-- strict thread matches above, loose matches on Subject: below --
2010-05-11 8:10 Tristan Ye
2010-05-11 9:53 Tristan Ye
2010-05-11 9:54 Tristan Ye
2010-05-11 10:40 ` tristan
2010-05-11 20:40 ` Joel Becker
2010-05-18 19:34 ` Joel Becker
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=4BE8B297.30708@oracle.com \
--to=tristan.ye@oracle.com \
--cc=ocfs2-devel@oss.oracle.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).