From: Kalpak Shah <kalpak@clusterfs.com>
To: Theodore Tso <tytso@MIT.EDU>
Cc: linux-ext4@vger.kernel.org
Subject: Re: [PATCH 0 of 4] Check journal inode sanity and recreate journal
Date: Fri, 22 Jun 2007 02:15:09 +0530 [thread overview]
Message-ID: <1182458712.4483.3.camel@garfield> (raw)
In-Reply-To: <patchbomb.1182445207@candygram.thunk.org>
On Thu, 2007-06-21 at 13:00 -0400, Theodore Tso wrote:
> Hi Kalpak,
>
> I've broken up your patch and rewritten portions of them to
> clean them up. As I've mentioned before, smaller patches are easier to
> review and to cherry pick as necessary.
Thanks. Will certainly split the patches whenever possible while
submitting them henceforth.
Thanks,
Kalpak.
prev parent reply other threads:[~2007-06-21 20:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-21 17:00 [PATCH 0 of 4] Check journal inode sanity and recreate journal Theodore Tso
2007-06-21 17:00 ` [PATCH 1 of 4] Add default journal size function Theodore Tso
2007-06-21 17:00 ` [PATCH 2 of 4] Recreate journal that had been removed previously due to corruption Theodore Tso
2007-06-21 17:00 ` [PATCH 3 of 4] Write the updated journal inode if s_jnl_blocks was successfully used Theodore Tso
2007-06-21 17:00 ` [PATCH 4 of 4] e2fsck: Check the all of journal blocks for validity Theodore Tso
2007-06-21 20:45 ` Kalpak Shah [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=1182458712.4483.3.camel@garfield \
--to=kalpak@clusterfs.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