Thread (152 messages) flat view 152 messages, 23 authors, 2016-06-15

Re: git on MacOSX and files with decomposed utf-8 file names

From: Johannes Schindelin <hidden>
Date: 2016-06-15 22:44:06

Hi,

On Thu, 17 Jan 2008, Pedro Melo wrote:
On Jan 17, 2008, at 12:33 AM, Johannes Schindelin wrote:
quoted
On Wed, 16 Jan 2008, Linus Torvalds wrote:
quoted
So if you are a case-insensitive filesystem, then normalization is 
sane.
Actually, no.  Even an case-challenged filesystem should keep the 
_original_ name around, if only for the exact same argument you used 
earlier: if the user chooses to capitalise some letters, but not 
others, it is not the filesystem's place to "correct" that.
For the record, HFS+ is case-insensitive but case-preserving so I 
believe they keep the original filename around.
For the record, that's only the default setting.  AFAIK you can configure 
it to care about case, too.

Also for the record, the whole thread was about HFS+ _not_ keeping the 
original filename around, but _only_ a normalised version of it.
But I think that focusing on HFS+ is loosing sight of the real problem. 
It's not about encoding at the filesystem, but encoding inside the git 
structures.
So far I have not seen anyone talking _seriously_ about this issue.  Only 
a few shouts "you should support", and a few shouts back "I don't care 
about insane filesystems".

Therefore, I fully agree with you that we're losing sight of the real 
problem.

Ciao,
Dscho
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help