Hi,
On Jan 17, 2008, at 6:18 PM, Johannes Schindelin wrote:
On Thu, 17 Jan 2008, Pedro Melo wrote:
On Jan 17, 2008, at 6:09 PM, Mark Junker wrote:
IMHO it would be the best solution when git stores all string meta
data in UTF-8 and converts it to the target systems file system
encoding. That would fix all those problems with different
locales and
file system encodings ...
+1.
-1.
It's just too arrogant to force your particular preferences down the
throat of every git user.
Do you agree that you need to store or at least calculate a
normalized version of each filename to see if you are already
tracking the file, to take in account all the the filesystems out
there who are not case-preserving, case-sensitive?
If so, do you think those rules should be an option? Or a preference?
Should I specify in my config file that I want my filenames to be
normalized?
Ignoring encoding, and case-sensitive issues in the git index creates
problems for those people who want/need to use non-ascii chars in
their filenames, and have some change of being able to collaborate
with other users on different operating systems.
Best regards,
--
Pedro Melo
Blog: http://www.simplicidade.org/notes/
XMPP ID: melo@xxxxxxxxxxxxxxxx
Use XMPP!
-
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
