The commit 2db3d30 added the following file:
It seems like this file path is too long for either Windows or Git on Windows. If you pull/merge this commit, the file cannot be created, if you do a clean clone, this file is deleted immediately and cannot be restored.
Suggestion: use a shorter file name.
[TASK] Windows issues with long file names in Git sources
The recent DataHander functional tests integrate file names that
are very long since they contain a description of what actually
is expected in the accordant test assertion file.
However, Windows has a limit of 260 characters per file path.
The longest file path of the mentioned functional tests has been
223 characters and is now reduced to 166 characters.
Reviewed-by: Marc Bastian Heinrichs
Reviewed-by: Oliver Hader
Tested-by: Oliver Hader
#1 Updated by Eric Chavaillaz over 6 years ago
Windows allows something like this on NTFS partition :
C:\<256 character length><NULL>
The file in question is long of 223 characters.
So if you got something like C:\Users\Your Name\Documents\Git\typo3_src-git\typo3..., the length will be 223 + 45 (Users\Your Name\Documents\Git\typo3_src-git\) = 268 characters.
It's too long. You can move the location of your Git repository in local to solve quickly the problem.
But I agree that this file is too long!
#2 Updated by Philipp Gampe over 6 years ago
- Status changed from New to Accepted
More information on windows path limitations: http://msdn.microsoft.com/en-us/library/aa365247(VS.85).aspx
The nineties strike back! Yeah.
One would assume that modern operating systems and shells as well as GUIs support more than byte long path pointers, but well ... we need to fix this.