From: Erik Andersen <andersen@codepoet.org>
To: Jens Benecke <jens-usenet@spamfreemail.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Dangerout FAT32 filesystem bug
Date: Sun, 18 Jan 2004 12:51:14 -0700 [thread overview]
Message-ID: <20040118195114.GA11910@codepoet.org> (raw)
In-Reply-To: <6515944.C7MQEJGAfx@spamfreemail.de>
On Sun Jan 18, 2004 at 08:39:50PM +0100, Jens Benecke wrote:
> OGAWA Hirofumi wrote:
>
> > Jens Benecke <jens-usenet@spamfreemail.de> writes:
> >
> >> Hi,
> >>
> >> I didn't find anything in the changelog for 2.6.[01] and 2.4.2[2345]:
> >> has the FAT32 FS bug mentioned (and successfully fixed/patched) in
>
> > 2.6 was already fixed several months ago.
> > For 2.4, patch submited.
>
> That's very strange, as I couldn't find any mention of it in the 2.6
> changelogs since Dec 05 (when it was first submitted to lkml).
>
> OK, maybe I didn't look hard enough.
>
> Thanks. :)
It has been in 2.6 for quite some time now,
-Erik
--
Erik B. Andersen http://codepoet-consulting.com/
--This message was written using 73% post-consumer electrons--
prev parent reply other threads:[~2004-01-18 19:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-18 11:24 Dangerout FAT32 filesystem bug Jens Benecke
2004-01-18 15:01 ` OGAWA Hirofumi
2004-01-18 19:39 ` Jens Benecke
2004-01-18 19:51 ` Erik Andersen [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=20040118195114.GA11910@codepoet.org \
--to=andersen@codepoet.org \
--cc=jens-usenet@spamfreemail.de \
--cc=linux-kernel@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