From: "Theodore Ts'o" <tytso@mit.edu>
To: Gabriel Krisman Bertazi <krisman@collabora.com>
Cc: linux-ext4@vger.kernel.org
Subject: Re: [PATCH v7 00/10] Ext4 case-insensitive support
Date: Thu, 25 Apr 2019 16:35:17 -0400 [thread overview]
Message-ID: <20190425203517.GG4739@mit.edu> (raw)
In-Reply-To: <20190413192533.2549-1-krisman@collabora.com>
On Sat, Apr 13, 2019 at 03:25:23PM -0400, Gabriel Krisman Bertazi wrote:
>
> This is the v7 of the case-insensitive support. It includes the design
> changes we discussed, unicode 12.0 support, and the Linus' request about
> the way we store the utf8data.h file.
The V7 case insensitive support is now in the ext4.git tree. So it
should be in Linux-next tomorrow.
Cheers,
- Ted
prev parent reply other threads:[~2019-04-25 20:35 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-13 19:25 [PATCH v7 00/10] Ext4 case-insensitive support Gabriel Krisman Bertazi
2019-04-13 19:25 ` [PATCH v7 02/10] unicode: Introduce code for UTF-8 normalization Gabriel Krisman Bertazi
2019-04-13 19:25 ` [PATCH v7 04/10] unicode: Implement higher level API for string handling Gabriel Krisman Bertazi
2019-04-13 19:25 ` [PATCH v7 05/10] unicode: Introduce test module for normalized utf8 implementation Gabriel Krisman Bertazi
2019-04-13 19:25 ` [PATCH v7 07/10] MAINTAINERS: Add Unicode subsystem entry Gabriel Krisman Bertazi
2019-04-13 19:25 ` [PATCH v7 08/10] ext4: Include encoding information in the superblock Gabriel Krisman Bertazi
2019-04-13 19:25 ` [PATCH v7 09/10] ext4: Support case-insensitive file name lookups Gabriel Krisman Bertazi
2019-04-13 19:25 ` [PATCH v7 10/10] docs: ext4.rst: Document case-insensitive directories Gabriel Krisman Bertazi
2019-04-16 19:44 ` [PATCH 1/2] unicode: Update unicode database unicode version 12.1.0 Gabriel Krisman Bertazi
2019-04-16 19:44 ` [PATCH 2/2] ext4: Update to use unicode 12.1 Gabriel Krisman Bertazi
2019-04-25 20:35 ` Theodore Ts'o [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=20190425203517.GG4739@mit.edu \
--to=tytso@mit.edu \
--cc=krisman@collabora.com \
--cc=linux-ext4@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).