RE: [PATCH] Re: Gitk --all error when there are more than 797 refs in a repository

From: Murphy, John <john.murphy@bankofamerica.com>
Date: Sep 21, 2009, 14:02 UTC
Message-ID: <6F87406399731F489FBACE5C5FFA0458518DE8@ex2k.bankofamerica.com>
In-Reply-To: <19124.8378.975976.347711@cargo.ozlabs.ibm.com>

Johannes Sixt writes:

> I cannot reproduce the error. I have a repository with 100 commits in

> linear history and 5000 refs (50 refs per commit). They are named
> refs/heads/branch-XXXX. I don't see any problems with 'gitk --all'.

That still leave you with only 100 unique refs. You need over 797 unique refs.

> The error must be in some other git invocation.

I put many debug pop-ups around the code and I believe that this the call that is dying on. This is the only part of the code that has the error text "fatal: ambiguous argument".

Paul Mackerras writes:

Show 5 quoted lines

> I knew about the 32k command-line limit under windows, but I don't see
> how that applies in this case unless it is $revs that is too long (and
> if that is the case then I don't see how your patch helps).  Is there
> also a 32k limit on the size of data returned by a command executed
> with [exec]?

In this case $revs is "--all"

I believe what I am experiencing is a 32K limit with [exec]

Additional info: My repo has: 17,737 commits