Hi,
On Jan 17, 2008, at 6:44 PM, Linus Torvalds wrote:
Correct. Storing or using a normalized version of the filename is
only part of the problem.
The full problem is:
User A <-> filesystem A <-#-> git < ...... > git <-#-> filesystem B <-
> user B.
You have to encode/decode/normalize on all the <-#-> and there is no
magic bullet. Each user would have to tell git "Hey I'm using utf-8"
or "Hey, I'm a masochist using HFS+".
But I think its important for git to store the filenames in something
that at least permits this kind of scenario.
All encoding/decoding/normalization is of course optional, and for
git, it still is a sequence of bytes.
Correct. HFS+ has bigger problems. I'm not sure if this is enough to
solve it.
But it would solve two linux users using different encodings.
And given that the filtering layers are optional, you have to
configure them, it wont bite nobody.
Best regards,
--
Pedro Melo
Blog: http://www.simplicidade.org/notes/
XMPP ID: melo@simplicidade.org
Use XMPP!
-
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html