public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: David Woodhouse <dwmw2@infradead.org>
To: Jarkko Lavinen <jarkko.lavinen@nokia.com>
Cc: MTD List <linux-mtd@lists.infradead.org>
Subject: Re: JFFS2 case insensitivity
Date: Fri, 20 Feb 2004 21:01:18 +0000	[thread overview]
Message-ID: <1077310878.427.722.camel@hades.cambridge.redhat.com> (raw)
In-Reply-To: <20040127134835.GA9404@angel.research.nokia.com>

On Tue, 2004-01-27 at 15:48 +0200, Jarkko Lavinen wrote:
> My primary concern was to estimate the cost or pain of implementing
> file name case insensitivity and find arguments against doing it in
> the kernel.

See the linux-kernel mailing list (search for 'UTF-8 and
case-insensitivity').

-- 
dwmw2

  parent reply	other threads:[~2004-02-20 21:01 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-27 10:06 JFFS2 case insensitivity Jarkko Lavinen
2004-01-27 11:13 ` David Woodhouse
2004-01-27 13:48   ` Jarkko Lavinen
2004-01-27 15:18     ` David Woodhouse
2004-01-27 22:49       ` Charles Manning
2004-01-28  6:13         ` David Woodhouse
2004-02-20 21:01     ` David Woodhouse [this message]
2004-01-27 13:48 ` David Woodhouse

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=1077310878.427.722.camel@hades.cambridge.redhat.com \
    --to=dwmw2@infradead.org \
    --cc=jarkko.lavinen@nokia.com \
    --cc=linux-mtd@lists.infradead.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