From: Mark Fasheh <mfasheh@suse.com>
To: Theodore Tso <tytso@mit.edu>
Cc: Jan Kara <jack@suse.cz>,
linux-ext4@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>,
ocfs2-devel@oss.oracle.com
Subject: Re: [PATCH 3/3] ocfs2: Add journal parameter to jbd2_journal_begin_ordered_truncate()
Date: Wed, 11 Feb 2009 13:01:28 -0800 [thread overview]
Message-ID: <20090211210128.GD17410@wotan.suse.de> (raw)
In-Reply-To: <20090210151255.GE30689@mini-me.lan>
On Tue, Feb 10, 2009 at 10:12:55AM -0500, Theodore Tso wrote:
> The problem with separating out the patch into three separate commits
> is that it can potentially break a "git bisect". To fix this, I
> believe the right thing to do is to combine the three patches into a
> single commit, and to push this via the ext4 tree; any objections?
That's fine with me. Btw, you forgot my:
Acked-by: Mark Fasheh <mfasheh@suse.com>
--Mark
--
Mark Fasheh
next prev parent reply other threads:[~2009-02-11 21:01 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-05 14:52 [PATCH 0/3] Fix possible NULL pointer dereference in JBD2 Jan Kara
2009-02-05 14:53 ` [PATCH 1/3] jbd2: Fix possible NULL pointer dereference in jbd2_journal_begin_ordered_truncate() Jan Kara
2009-02-05 14:53 ` [PATCH 2/3] ext4: Add journal parameter to jbd2_journal_begin_ordered_truncate() Jan Kara
2009-02-05 14:53 ` [PATCH 3/3] ocfs2: " Jan Kara
2009-02-10 3:19 ` [Ocfs2-devel] " Joel Becker
2009-02-10 15:12 ` Theodore Tso
2009-02-11 9:25 ` Jan Kara
2009-02-11 21:01 ` Mark Fasheh [this message]
2009-02-05 19:32 ` [PATCH 0/3] Fix possible NULL pointer dereference in JBD2 Mark Fasheh
2009-02-05 21:37 ` Theodore Tso
2009-02-09 17:34 ` Jan Kara
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=20090211210128.GD17410@wotan.suse.de \
--to=mfasheh@suse.com \
--cc=akpm@linux-foundation.org \
--cc=jack@suse.cz \
--cc=linux-ext4@vger.kernel.org \
--cc=ocfs2-devel@oss.oracle.com \
--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).