From: Konrad Karl <kk_konrad@gmx.at>
To: git@vger.kernel.org
Subject: Re: git gui blame: git-blame loops at 100% cpu
Date: Sun, 18 Apr 2010 23:52:10 +0200 [thread overview]
Message-ID: <20100418215210.GA19776localhost> (raw)
In-Reply-To: <20100417231327.162560@gmx.net>
Replying to myself
> Everything seems to be working fine but git gui blame some_file seems to
> procedure correct output in the file viewer but the progress bar stops
> at 1271 of 2783 lines for one specific file and then the git-blame process
> consumes 100% cpu.
Grr, this was a false alarm. It finishes after about 4 Minutes and I
did not wait that long. git gui was using git-blame -C -C40.
gui.fastcopyblame=true seems to help to get sane runtimes.
(this can be achieved by checkin "Blame Copy Only On Changed Files"
in git gui options dialog -kudos to charon in #git for this suggestion)
Perhaps this should be made the default?
Konrad
next prev parent reply other threads:[~2010-04-18 21:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-17 23:13 git gui blame: git-blame loops at 100% cpu Konrad Karl
2010-04-18 21:52 ` Konrad Karl [this message]
2010-04-18 21:52 ` Konrad Karl
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=20100418215210.GA19776localhost \
--to=kk_konrad@gmx.at \
--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 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.