Invalid path error for files during clone which gets autodeleted after irrelevant commit

[GoogleCodeExporter]

What steps will reproduce the problem?
-------------------------------------
On a Windows 8 machine, clone a repo containing files such as:
rootPath/path/some_dirpath/a_too_long_filename_["parameter",138436140,135548799,
0,"somet:hing",{"another":"value","paramer":10},40,"","error"]

What is the expected output?
----------------------------
1. That a warning is triggered instead of an error. 
2. Preferably, that the files are checked out, despite that the file name/path 
indeeds seems a bit off.
3. That I am able to commit changes in irrelevant files (= in a whole other 
directory) without seeing those file's marked as deleted in my commit GUI.
4. After unchecking all the files for commit, that the files will not be 
auto-committed as deleted. 

What do you see instead?
------------------------
In the log, I see the following error for each error:
"error: Invalid path '<the path which is not accepted>'".

And the log ends with:
Checking out files: 100% (total/sametotal), done.
Success (10000 ms @ 2/6/2015 5:06:30 PM)

However, the files are not available.

Additionally, when I commit changes in irrelevant files, these missing files 
are shown in the changes los as "Deleted". And I am not able to revert these or 
even add to the git ignore list. And after unchecking these files (I don't want 
to simply delete those files from the repo as they are not minde) and 
committing the changes that I actually want to commit... these files have get 
deleted from the repo. You however don't notice this, until you check the git 
log.

Version information
-------------------
Windows 8.1
TortoiseGit 1.8.12.0 (C:\Program Files\TortoiseGit\bin\) 
git version 1.9.5.msysgit.0 (C:\Program Files (x86)\Git\bin) 

Additional information
----------------------
Despite that I think that these files should not exists... they are not mine 
and should not be auto-deleted.

Original issue reported on code.google.com by vint...@gmail.com on 6 Feb 2015 at 4:35

[GoogleCodeExporter]

Could you please provide the testing repository?
Phehaps it is on Github or some public place, so that I can test the clone and 
go on easily.

Is the lenght of problematic filename over 260 charactors?
Perhaps it is the long path filename(>260) problem.
Then, I recommend that make sure the lenght of filename does not over 260 
charactors limit(the MAX_PATH).

Consider that the repository is not created/controlled by you.
You may want "git config --global core.longpaths true", but NOTE that it is not 
recommended.

Also, there are some refs:
https://github.com/msysgit/msysgit/issues/227
https://github.com/msysgit/git/pull/212

Original comment by yuelinho...@gmail.com on 7 Feb 2015 at 5:27

[GoogleCodeExporter]

Unfortunately, I am not able to provide the repository as the repository is 
private (it belongs to the company that I work for) and the repository is not 
created nor controlled by me.

The filenames that I checked are not over 260 characters. I however did update 
the configuration as provided but as expected, that does not seem to resolve 
the issue.

Any other ideas? I am the only one using TortoiseGIT here and I would love to 
keep using it although I am not able to commit nor push my changes like this.

Original comment by vint...@gmail.com on 9 Feb 2015 at 8:41

[GoogleCodeExporter]

Try to create a dummy testing repository!?

Perhaps try to capture the debug strings for more information.
Please see 
https://code.google.com/p/tortoisegit/wiki/HOWTO_Debug#Capture_Debug_Strings

Original comment by yuelinho...@gmail.com on 9 Feb 2015 at 12:27

[GoogleCodeExporter]

I'm sorry, but this isn't a TortoiseGit issue. Git for Windows, on which 
TortoiseGit relies, cannot handle such paths on Windows. I'm not aware of 
workarounds - these files need to be removed from the repository.

Original comment by sstrickr...@googlemail.com on 29 Mar 2015 at 3:49

• Changed state: ThirdPart

[GoogleCodeExporter]

This issue has come with installing the latest git version (git version 
1.9.5.msysgit.0). It is of course a windows problem but with the previous 
version it worked for me.

Original comment by niy...@gmail.com on 16 Jun 2015 at 9:30