git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dan Zwell <dzwell@zwell.net>
To: Git Mailing List <git@vger.kernel.org>
Subject: git-gui is slow to display a large number of changed/new files
Date: Mon, 29 Jun 2009 16:19:54 -0500	[thread overview]
Message-ID: <4A492FFA.5030703@zwell.net> (raw)

Hello,

I was recently working on a project with tens of thousands of generated 
files. The generated directory was not intended to be tracked by git, 
but I had forgotten to add it to .gitignore. When I tried to use 
git-gui, it seemed to hang for about a minute. The problem is that 
creating the icons in the "staged changes" and "unstaged changes" 
windows is very slow. This data is redisplayed after several operations, 
and the lag makes git-gui unusable.

Is this behavior worth changing? I doubt the scenario I encountered is a 
common one. 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.

Thanks
-Daniel

             reply	other threads:[~2009-06-29 21:27 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-29 21:19 Dan Zwell [this message]
2009-06-30 14:47 ` git-gui is slow to display a large number of changed/new files Alex Riesen

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=4A492FFA.5030703@zwell.net \
    --to=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).