[git-users] gitk: file name too long
Hi, I'm using git on windows 7 and lately I've been getting the following message whenever I try to refresh my gitk view: "Error executing git log: couldn't execute "git": file name too long" After some research this issue seems to be fixed, see https://code.google.com/p/msysgit/issues/detail?id=387. So I upgraded to 1.8.5.2.mysysgit.0 but I am still getting the problem. None of my colleagues who are working with the same repository have the problem and I have already shortened the path the my clone directory. Any hints on how I could proceed trying to fix this? Thanks in advance, Tom -- You received this message because you are subscribed to the Google Groups "Git for human beings" group. To unsubscribe from this group and stop receiving emails from it, send an email to git-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: [git-users] gitk: file name too long
Op donderdag 30 januari 2014 11:40:13 UTC+1 schreef Konstantin Khomoutov: > > Still, could you please disclose what is the full pathname of your > repository and what is the pathname of the offending file in the > repository? If you can't detect the offending file, you could try to > infer what it is--I presume you should have been looking at that file's > diff or commit log in gitk. > > You might consider to not post this data here but rather do the > calculation yourself: the length of the name of the file in your repo > must be under MAX_PATH characters which is 260 [1]. > > As to different behaviour of gitk between your development > workstations... does the situation change if you set the knob "patch / > files" atop of the bottom-right window to "files"? > > 1. http://msdn.microsoft.com/en-us/library/aa365247 > Hi, I tried seeing what the knob patch/files was set to but in my view it only showed patch/tree as options. Trying either setting did not solve the problem but it did cause me to try and search for a 'files' like setting. In the view menu I have the option to select All files/Command line/All branches. This option was set to Command line for me and once I set it to 'All branches' the problem did not occur again. I have no idea what exactly these settings mean but I consider my problem solved. Thanks for the pointers. -- You received this message because you are subscribed to the Google Groups "Git for human beings" group. To unsubscribe from this group and stop receiving emails from it, send an email to git-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
