From: Theodore Tso <tytso@MIT.EDU>
To: Aneesh Kumar <aneesh.kumar@gmail.com>
Cc: linux-ext4 <linux-ext4@vger.kernel.org>
Subject: Re: ext4_avoid_panic_in_case_of_corrupted_bitmap.patch
Date: Sun, 10 Feb 2008 19:21:32 -0500 [thread overview]
Message-ID: <20080211002132.GH21729@mit.edu> (raw)
In-Reply-To: <cc723f590802090735w67cc7b0bjf2efcceae1e85f06@mail.gmail.com>
On Sat, Feb 09, 2008 at 07:35:03AM -0800, Aneesh Kumar wrote:
> I guess we pushed an old version of this patch. I had set in -ver2.
> with better comments.
>
> http://article.gmane.org/gmane.comp.file-systems.ext4/4956
>
Sorry, I saw your note, but I missed it when I was doing prepping the
branch to for the git pull request.
We can prepare a comments-only patch which we can merge either before
-rc2 if Linus is willing, or worst case keep it in the ext4 patch
queue until the next merge window.
Again, sorry for missing the updated patch!
- Ted
prev parent reply other threads:[~2008-02-11 0:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-09 15:35 ext4_avoid_panic_in_case_of_corrupted_bitmap.patch Aneesh Kumar
2008-02-11 0:21 ` Theodore Tso [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=20080211002132.GH21729@mit.edu \
--to=tytso@mit.edu \
--cc=aneesh.kumar@gmail.com \
--cc=linux-ext4@vger.kernel.org \
/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).