From: Alex Riesen <raa.lkml@gmail.com>
To: Dan Zwell <dzwell@zwell.net>
Cc: Git Mailing List <git@vger.kernel.org>
Subject: Re: git-gui is slow to display a large number of changed/new files
Date: Tue, 30 Jun 2009 16:47:27 +0200 [thread overview]
Message-ID: <81b0412b0906300747id528b76ue48d0bf1ba3709fe@mail.gmail.com> (raw)
In-Reply-To: <4A492FFA.5030703@zwell.net>
2009/6/29 Dan Zwell <dzwell@zwell.net>:
> Is this behavior worth changing? I doubt the scenario I encountered is a
> common one.
It happens. There are imported repositories, and things like CVS/SVN/Perforce
force people to do giant commits. So yes, it definitely is worth looking into.
> ... However, I have written a patch to display at most 5000
> changed/new files, warning the user that the list has been truncated. If
> this is a worthy change, I can submit the patch--I can also change it so
> that the maximum number of displayed files is taken from git's
> configuration.
Even 5000 is insane, so that would be a good start, for sure.
Paul Mackerras is gitk's maintainer, remember to put him on Cc:
prev parent reply other threads:[~2009-06-30 14:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-29 21:19 git-gui is slow to display a large number of changed/new files Dan Zwell
2009-06-30 14:47 ` Alex Riesen [this message]
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=81b0412b0906300747id528b76ue48d0bf1ba3709fe@mail.gmail.com \
--to=raa.lkml@gmail.com \
--cc=dzwell@zwell.net \
--cc=git@vger.kernel.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 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 NNTP newsgroup(s).