From: Johannes Sixt <j.sixt@viscovery.net>
To: "Murphy, John" <john.murphy@bankofamerica.com>
Cc: Paul Mackerras <paulus@samba.org>,
Pat Thoyts <patthoyts@users.sourceforge.net>,
git@vger.kernel.org
Subject: Re: [PATCH] Re: Gitk --all error when there are more than 797 refs in a repository
Date: Mon, 21 Sep 2009 16:09:20 +0200 [thread overview]
Message-ID: <4AB78910.7010402@viscovery.net> (raw)
In-Reply-To: <6F87406399731F489FBACE5C5FFA0458518DE8@ex2k.bankofamerica.com>
Murphy, John schrieb:
> Paul Mackerras writes:
>
>> 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]
But in order to have a $revs that exceeds 32K, you would already have to
invoke gitk with a huge command line that exceeds the limit (but this is
not possible), no?
How do you run gitk?
-- Hannes
next prev parent reply other threads:[~2009-09-21 14:09 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-17 19:07 Gitk --all error when there are more than 797 refs in a repository Murphy, John
2009-09-18 14:06 ` [PATCH] " Pat Thoyts
2009-09-18 15:16 ` Johannes Sixt
2009-09-19 0:07 ` Paul Mackerras
2009-09-21 14:02 ` Murphy, John
2009-09-21 14:09 ` Johannes Sixt [this message]
2009-09-21 14:11 ` Murphy, John
2009-09-21 15:59 ` Johannes Sixt
2009-09-21 23:56 ` Pat Thoyts
2009-09-22 1:23 ` Murphy, John
2009-09-22 1:39 ` Junio C Hamano
2009-09-22 1:47 ` Junio C Hamano
2009-09-22 22:48 ` Pat Thoyts
2009-11-03 10:04 ` Alex Riesen
2009-11-03 10:41 ` Paul Mackerras
2009-09-22 23:30 ` Paul Mackerras
2009-09-23 0:02 ` Junio C Hamano
2009-11-03 9:40 ` Paul Mackerras
2009-11-03 14:59 ` Junio C Hamano
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:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4AB78910.7010402@viscovery.net \
--to=j.sixt@viscovery.net \
--cc=git@vger.kernel.org \
--cc=john.murphy@bankofamerica.com \
--cc=patthoyts@users.sourceforge.net \
--cc=paulus@samba.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* 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.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.