From: Christoph Hellwig <hch@lst.de>
To: OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>
Cc: Christoph Hellwig <hch@lst.de>,
chris.mason@oracle.com, linux-fsdevel@vger.kernel.org
Subject: Re: vfat vs msdos and -o flush
Date: Tue, 9 Mar 2010 13:57:06 +0100 [thread overview]
Message-ID: <20100309125706.GA18345@lst.de> (raw)
In-Reply-To: <87sk8cgqup.fsf@devron.myhome.or.jp>
On Sun, Mar 07, 2010 at 11:15:42PM +0900, OGAWA Hirofumi wrote:
> [BTW, I was thinking in past, just kill msdos and adds new shortname
> only option to vfat. ;)]
Sounds even better to me. But I'm not uptodate on vfat internals enough
to decide whether that's easily doable. We still can do that after
the consolidation I suggested above.
next prev parent reply other threads:[~2010-03-09 12:57 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-01 17:08 vfat vs msdos and -o flush Christoph Hellwig
2010-03-03 13:36 ` OGAWA Hirofumi
2010-03-07 11:00 ` OGAWA Hirofumi
2010-03-07 13:06 ` Christoph Hellwig
2010-03-07 14:15 ` OGAWA Hirofumi
2010-03-09 12:57 ` Christoph Hellwig [this message]
2010-03-09 13:42 ` Chris Mason
2010-03-10 19:19 ` Jeff Mahoney
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=20100309125706.GA18345@lst.de \
--to=hch@lst.de \
--cc=chris.mason@oracle.com \
--cc=hirofumi@mail.parknet.co.jp \
--cc=linux-fsdevel@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).