From: Linus Torvalds <torvalds@linux-foundation.org>
Date: Thu, 14 May 2009 22:51:46 GMT
Subject: Re: [PATCH 3/3] read_directory(): infrastructure for pathname character set conversion
Message-ID: <alpine.LFD.2.01.0905141547480.3343@localhost.localdomain>
In-Reply-To: <727e50150905141536r5f3c4c1ap615166ba71018bf3@mail.gmail.com>



On Thu, 14 May 2009, Aaron Cohen wrote:
> 
> Does this possibly allow using the magic "\\?\" prefix on windows to
> avoid file name length restrictions?

That would be the intention - eventually. The point being exactly that the 
'path' side can be done differently from the 'basename' part that git then 
uses internally.

However, the thing is not complete. As shown from the strace, almost all 
filesystem operations then end up using the 'git internal' name anyway. 
It's currently literally just the filesystem traversal itself that knows 
to separate the notion of 'internal pathname representation' from the 
filesystem accesses.

So right now, the only thing that uses the filesystem-specific stuff is 
the "opendir()" (and the lstat() in case the filesystem doesn't support 
d_type in the dirent).

		Kubys