list mirror (unofficial, one of many)
 help / color / mirror / code / Atom feed
From: Bret Barkelew <>
To: Bryan Turner <>
Subject: Re: git version throws file name too long in gitk
Date: Thu, 3 Jan 2019 19:38:04 -0800	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

They are the exact same path (with a different drive letter).

Another thing I've been able to confirm is I uninstalled git 2.20.1
and installed 2.19.0 on the failing system, and the older version of
Git works.
I've also tried a suggested fix I saw elsewhere to enable long path
names in the Windows registry, which did not resolve the issue with
git 2.20.1.

Happy to collect any additional data.
- Bret

On Thu, Jan 3, 2019 at 7:10 PM Bryan Turner <> wrote:
> On Thu, Jan 3, 2019 at 6:21 PM Bret Barkelew <> wrote:
>> When I open gitk in a particular repository under this version of Git
>> for Windows, I now get a dialog box that says "Error: couldn't execute
>> "git": file name too long". I've noticed that the most pronounced
>> effect is that I cannot see the file diffs (or sometimes the file name
>> list) for any of the commits. I don't know the exact repro, but I've
>> narrowed down the following things:
>> - This does not happen with the same repo if I use a system that has
>> git on another machine.
>> - This does not happen on my current machine in a freshly cloned repo.
> How “deep” are the paths to the different clones on the different systems? Are all of the clones at exactly the same path on disk?
> Git on Windows is (by defaulted) limited by MAX_PATH, which is 260 characters. That length is calculated including the path to the repository itself and then to the file inside the repository. That means, for example, a given repository cloned to C:\repo may not have issues, but the same repository cloned to C:\Users\Bryan\Documents\workspaces\repo may.
>> However, as soon as the remote updates with any changes on a given
>> fetch/pull, the repo is put in a bad state permanently.
>> I've pasted the output from gitk below...
>> couldn't execute "git": file name too long
>> couldn't execute "git": file name too long
>>     while executing
>> "open $cmd r"
>>     (procedure "getallcommits" line 48)
>>     invoked from within
>> "getallcommits"
>>     (procedure "readcache" line 80)
>>     invoked from within
>> "readcache file827e200"
>>     ("eval" body line 1)
>>     invoked from within
>> "eval $script"
>>     (procedure "dorunq" line 11)
>>     invoked from within
>> "dorunq"
>>     ("after" script)
>> Happy to gather whatever data needed.
>> Thanks!
>> - Bret Barkelew

  parent reply	other threads:[~2019-01-04  3:39 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-04  2:21 Bret Barkelew
     [not found] ` <>
2019-01-04  3:38   ` Bret Barkelew [this message]
2019-01-09 18:39     ` Johannes Schindelin
2019-01-09 18:48       ` Bret Barkelew
2019-01-10 15:19         ` Johannes Schindelin
2019-01-10 18:55           ` Bret Barkelew
2019-04-18 18:16             ` Bret Barkelew
2019-04-27 23:20               ` Johannes Schindelin
2019-05-29 16:40                 ` Bret Barkelew
2019-05-29 18:07                   ` Johannes Schindelin

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:

  List information:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this inbox:

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).