From: OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>
To: "Albert D. Cahalan" <acahalan@cs.uml.edu>
Cc: msmith@operamail.com (Malcolm Smith),
linux-kernel@vger.kernel.org, chaffee@cs.berkeley.edu
Subject: Re: [RFC] FAT extension filters
Date: Wed, 15 May 2002 21:39:53 +0900 [thread overview]
Message-ID: <87u1p960va.fsf@devron.myhome.or.jp> (raw)
In-Reply-To: <200205150318.g4F3IPY103245@saturn.cs.uml.edu>
"Albert D. Cahalan" <acahalan@cs.uml.edu> writes:
> Also I found a bug in the vfat code. It doesn't
> properly handle old (pre-vfat) files with names
> that start with 0xE5; these are stored on disk
> with 0x05 as the first character.
Umm... why? 0xE5 is free entry mark.
--
OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>
next prev parent reply other threads:[~2002-05-15 12:40 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-15 2:38 [RFC] FAT extension filters Malcolm Smith
2002-05-15 3:18 ` Albert D. Cahalan
2002-05-15 12:39 ` OGAWA Hirofumi [this message]
2002-05-15 17:49 ` Albert D. Cahalan
2002-05-15 18:05 ` Mark Mielke
2002-05-15 18:42 ` Albert D. Cahalan
2002-05-16 13:46 ` OGAWA Hirofumi
2002-05-15 12:49 ` Xavier Bestel
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=87u1p960va.fsf@devron.myhome.or.jp \
--to=hirofumi@mail.parknet.co.jp \
--cc=acahalan@cs.uml.edu \
--cc=chaffee@cs.berkeley.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=msmith@operamail.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 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).