From: tristan <tristan.ye@oracle.com>
To: ocfs2-devel@oss.oracle.com
Subject: [Ocfs2-devel] [PATCH 2/3] Ocfs2: Change ocfs2_prepare_refcount_change_for_del() a bit to defer blocks reservation.
Date: Tue, 09 Feb 2010 09:19:11 +0800 [thread overview]
Message-ID: <4B70B80F.8000101@oracle.com> (raw)
In-Reply-To: <20100209005916.GH1832@mail.oracle.com>
Joel Becker wrote:
> On Thu, Jan 28, 2010 at 09:28:44AM +0800, tristan wrote:
>
>> TaoMa wrote:
>>
>>> Hi Tristan,
>>> you'd better integrate this patch with patch 3/3. otherwise we
>>> can't build successfully if we apply this one and don't apply the next
>>> one(in some git bisect case).
>>>
>> Yes I see, here I just split the patches as small as possible to be
>> logically separate, for the convenience of your reviewing:)
>>
>
> Tristan,
> Your instinct is good, but Tao is right, every commit has to
> compile and work. The next patches you work on, keep trying to break it
> up into logical things, but have working code. One of the best tricks
> is doing the isomorphic changes (changes that don't actually affect the
> behavior yet) first. I use this trick a lot. I can add an argument to
> a function or change what is passed through without actually changing
> the functionality. Once I've used this methodology to restructure the
> code, then I can change the behavior.
>
Joel, tao,
Your help really makes sense, thank you guys for sharing the experience:)
Tristan.
> For this particular change, I'm OK with it being one patch as I
> stated in my other email.
>
> Joel
>
>
next prev parent reply other threads:[~2010-02-09 1:19 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-27 11:22 [Ocfs2-devel] [PATCH 1/3] Ocfs2: Change ocfs2_remove_btree_range() a bit to consider refcount case Tristan Ye
2010-01-27 11:22 ` [Ocfs2-devel] [PATCH 2/3] Ocfs2: Change ocfs2_prepare_refcount_change_for_del() a bit to defer blocks reservation Tristan Ye
2010-01-27 22:16 ` TaoMa
2010-01-28 1:28 ` tristan
2010-02-09 0:59 ` Joel Becker
2010-02-09 1:19 ` tristan [this message]
2010-01-27 11:22 ` [Ocfs2-devel] [PATCH 3/3] Ocfs2: Treat ocfs2 truncate as a special case of punching holes Tristan Ye
2010-01-27 22:41 ` TaoMa
2010-01-28 1:36 ` tristan
2010-01-27 22:13 ` [Ocfs2-devel] [PATCH 1/3] Ocfs2: Change ocfs2_remove_btree_range() a bit to consider refcount case TaoMa
2010-01-28 2:17 ` tristan
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=4B70B80F.8000101@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.