Re: Re: Moving a directory into another fails
- From
Jakub Narebski <jnareb@gmail.com>
- Date
- Dec 4, 2006, 18:56 UTC
- Message-ID
- <el1qtr$bca$1@sea.gmane.org>
- In-Reply-To
- <f3d7535d0612041019q4bda01a1k9938b056d51f8a78@mail.gmail.com>
Stefan Pfetzing wrote:
Show 5 quoted lines
> 2006/7/28, Petr Baudis <pasky@suse.cz>: >>> >>> mv: cannot stat `"gitweb/test/M\\303\\244rchen"': No such file or directory >>> > since when is this file in the official git.git tree?
Since merging in gitweb, Sat Jun 10, 2006.
> Its quite problematic when used on HFS+ because it uses UTF-16 internally IMHO. > > Git always thinks there is a new file in my git.git clone.
That is the problem that git tries to be content agnostict, and it includes being coding agnostic.
I personally think that because the same repository might be deployed on different systems with different file name encoding (and this is not something you have control over, contrary to commit/tag message encoding, and encoding in files), git should acquire core.filesystemEncoding configuration variable which would encode from filesystem encoding used in working directory and perhaps index to UTF-8 encoding used in repository (in tree objects) and perhaps index.
-- Jakub Narebski Warsaw, Poland ShadeHawk on #git