From: Christoph Hellwig <hch@infradead.org>
To: Gabriel Krisman Bertazi <krisman@collabora.com>
Cc: tytso@mit.edu, fstests@vger.kernel.org,
linux-ext4@vger.kernel.org,
"Lakshmipathi.G" <lakshmipathi.ganapathi@collabora.co.uk>
Subject: Re: [PATCH v2 2/2] ext4/036: Add tests for filename casefolding feature
Date: Thu, 6 Jun 2019 22:23:31 -0700 [thread overview]
Message-ID: <20190607052331.GA19838@infradead.org> (raw)
In-Reply-To: <20190606193138.25852-2-krisman@collabora.com>
On Thu, Jun 06, 2019 at 03:31:38PM -0400, Gabriel Krisman Bertazi wrote:
> From: "Lakshmipathi.G" <lakshmipathi.ganapathi@collabora.co.uk>
>
> This new test implements verification for the per-directory
> case-insensitive feature, as supported in the reference implementation
> in Ext4. Currently, this test only supports Ext4, but the plan is to
> run it in other filesystems, once they support the feature.
>
> For now, let it live in ext4 and we move to shared/ or generic/ when
> other filesystems supporting this feature start to pop up.
Please keep it in shared/ from the start. There isn't really anything
ext4 specific. In fact xfs already supports CI file systems, just
without utf8 tables for now.
next prev parent reply other threads:[~2019-06-07 5:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-06 19:31 [PATCH v2 1/2] common/casefold: Add infrastructure to test filename casefold feature Gabriel Krisman Bertazi
2019-06-06 19:31 ` [PATCH v2 2/2] ext4/036: Add tests for filename casefolding feature Gabriel Krisman Bertazi
2019-06-07 5:23 ` Christoph Hellwig [this message]
2019-06-07 13:32 ` Theodore Ts'o
2019-06-07 16:42 ` Eryu Guan
2019-06-07 16:08 ` [PATCH v2 1/2] common/casefold: Add infrastructure to test filename casefold feature Eryu Guan
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=20190607052331.GA19838@infradead.org \
--to=hch@infradead.org \
--cc=fstests@vger.kernel.org \
--cc=krisman@collabora.com \
--cc=lakshmipathi.ganapathi@collabora.co.uk \
--cc=linux-ext4@vger.kernel.org \
--cc=tytso@mit.edu \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.