Re: [PATCH/RFC v3 6/8] Add case insensitivity support when using git ls-files
- From
Ævar Arnfjörð Bjarmason <avarab@gmail.com>
- Date
- Oct 4, 2010, 19:17 UTC
- Message-ID
- <AANLkTikdiLRDBchYiZedATPS5ct0nSa6CahxuZiTk3x0@mail.gmail.com>
- In-Reply-To
- <201010042102.31336.j6t@kdbg.org>
On Mon, Oct 4, 2010 at 19:02, Johannes Sixt <j6t@kdbg.org> wrote:
Show 6 quoted lines
> On Montag, 4. Oktober 2010, Robin Rosenberg wrote: >> Is anyone thinking "unicode" around here? > > My recommendation these days is that you should not use git if you care about > Unicode filenames: git is tied to POSIX in this regard, which defines > filenames as streams of *bytes*.
A SCM is all about giving meaning to streams of bytes. Just because POSIX only says that filenames are \0-delimited blobs that doesn't mean you can't have some annotation elsewhere that says "hey, these blobs are in $encoding".
<insert another disclaimer here about implementing this being a huge task, but I'm just saying...>